bus_bw timer start happens when first NDP is connected and
stop happens when last peer is departed indication is received
from firmware. But as part of driver unload, driver issues
stop_bss and firmware doesn't send any NDP END indication after
receiving this. So the timer started as part of first NDP confirm
is not stopped.
Try to stop the timer after processing the sme_disconnect which
is issued as part of stop_adapter for NDI mode.
Also, in STA+NDI concurrency scenario, bus bandwidth timer is
stopped on STA disconnection since hdd_any_adapter_is_assoc
checks only for other active STA or SAP. Add an NDI active
check so that timer is not stopped when NDPs are present on
an NDI.
Change-Id: Ibec447846fefad153261830c34bf2fa914636c7a
CRs-Fixed: 2625586
According to new changes in kernel 5.4 version onwards, driver has to
provide the policy for a NL command to ve verified against while
registering wiphy to the kernel.
To accommodate these changes, add policy for all the following
vendor commands that are being registered in the driver
QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_START
QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_STOP
QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_GET_VALID_CHANNELS
QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_GET_CAPABILITIES
QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_GET_CACHED_RESULTS
QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_SET_BSSID_HOTLIST
QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_RESET_BSSID_HOTLIST
QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_SET_SIGNIFICANT_CHANGE
QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_RESET_SIGNIFICANT_CHANGE
QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_PNO_SET_LIST
QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_PNO_SET_PASSPOINT_LIST
QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_PNO_RESET_PASSPOINT_LIST
Change-Id: I664e59564642c25fad931aca37cbc696b0c53b49
CRs-Fixed: 2635225
According to new changes in kernel 5.2 version onwards, driver has to
provide the policy for a NL command to be verified against while
registering wiphy to the kernel.
To satisfy kernel 5.2 requirement add policy to following vendor
command as part of this change:
QCA_NL80211_VENDOR_SUBCMD_GET_CHAIN_RSSI
Change-Id: Id1d1f1ee339bcef83b714e33cc174f886fee5ce6
CRs-Fixed: 2634263
Copy desire channel to vdev mlme bss channel after vdev start,
several APIs used bss channel before it is filled, issue happens
like wrong max tx power is set.
Change-Id: Ib46b5b9eebc2000d703dc542c97f85281c0f376c
CRs-Fixed: 2636775
According to new changes in kernel 5.2 version onwards, driver has to
provide the policy for a NL command to be verified against while
registering wiphy to the kernel.
To satisfy kernel 5.2 requirement add policy to following vendor
command as part of this change:
QCA_NL80211_VENDOR_SUBCMD_EXTERNAL_ACS
Change-Id: If2e7aec3d6f6d98168e0ceededea8d86db7078d9
CRs-Fixed: 2634255
In certain case, the active SAP interface will be deleted by
__wlan_hdd_del_virtual_intf by upper layer. In that case,
we need to flush pmksa in SAP PMKID cache.
Change-Id: I9a152df7a4c27aef82664f039fbca18259d6b63a
CRs-Fixed: 2635424
Currently there is no check for vendor vht ie in lim fill
assoc indication param api. If a station fills its vhtcaps
in vendor vht ie in assoc request, lim does not fill
vhtcaps information in assoc indication params from
station's assoc request and it results in invalid caps info
in assoc indication to upper layers.
To avoid this issue, add a check to look for vendor vht caps
before copy of the vht caps to assoc indication from assoc
request.
Change-Id: If80136d9a923d23b7db3ebec1d49e6e4012e6dd2
CRs-Fixed: 2633003
Currently sar safety request response event is not getting
reset before it starts wait for completion in sar
unsolicited timer callback which may cause issues if this
event gets complete multiple times.
To avoid above issue, reset the sar safety request response
event before it starts wait for completion.
CRs-Fixed: 2634885
Change-Id: I47b8abd6e960acc4dd9eef43faebe7e34203c380
Currenlty the occupied channel list is not updated with the new
channel to which STA gets connected after CSA. This leads to non
updation of the scan_list in firmware with the new occupied
channel. So firmware goes for a full scan instead of partial scan
in case of roam scan trigger.
To mitigate this issue, update the occupied channel list with the
new channel after CSA, which will lead to updation of scan list in
firmware.
Change-Id: I21e9bdd3474ecd23e49aabf27c2a9978b158c2ce
CRs-Fixed: 2632943
The Qtime offset derived with a connected AP (master) are not
cleared on disconnect. This leads to storage of stale offset
values. So clear the stale Qtime offset values on disconnection.
Currently there is no information in ftm_time_sync sysfs entry
regarding which BSSID the Qtime offset values are derived.
Add the BSSID info in the sysfs entry.
Change-Id: Iac47bccffae005602469a658e5ca0bc9008ac4b4
CRs-Fixed: 2629822
According to new changes in kernel 5.2 version onwards, driver has to
provide the policy for a NL command to be verified against while
registering wiphy to the kernel.
To satisfy kernel 5.2 requirement add policy to following vendor
command as part of this change:
QCA_NL80211_VENDOR_SUBCMD_SET_SAR_LIMITS
Change-Id: Ic02df66a2937aa3e1fd6b6193fbe31b7b4141ba4
CRs-Fixed: 2634250
According to new changes in kernel 5.2 version onwards, driver has to
provide the policy for a NL command to be verified against while
registering wiphy to the kernel.
To satisfy kernel 5.2 requirement add policy to following vendor
command as part of this change:
QCA_NL80211_VENDOR_SUBCMD_CONFIGURE_TDLS
Change-Id: I181d9d5c4160847d4d1be98f2ce5fa2627b3972a
CRs-Fixed: 2634233
Add ini support for DFS Channel Ageout Time, the time upto which
DFS channel information such as beacon found is remembered.
This ini is used to set the ageout timer value from host to FW.
If not set, FW will disable ageout time.
This value is sent as a WMI_PDEV_PARAM_SET_DFS_CHAN_AGEOUT_TIME
as part of WMI_PDEV_SET_PARAM_CMDID.
Change-Id: I99553fa87a4025f03c52b4b387a414ba06c2c457
CRs-Fixed: 2625996
According to new changes in kernel 5.4 version onwards, driver has to
provide the policy for a NL command to be verified against while
registering wiphy to the kernel.
To satisfy kernel 5.4 requirement add policy to following vendor
command as part of this change:
QCA_NL80211_VENDOR_SUBCMD_OEM_DATA
Change-Id: Idf44f40763aa967681a3e5e9df43f259b0254b61
CRs-Fixed: 2635048
According to new changes in kernel 5.4 version onwards, driver has to
provide the policy for a NL command to be verified against while
registering wiphy to the kernel.
To satisfy kernel 5.4 requirement add policy to following vendor
command as part of this change:
QCA_NL80211_VENDOR_SUBCMD_BEACON_REPORTING
Change-Id: I2f7cba7cb16d4a13fab33398e3034e71902317f3
CRs-Fixed: 2635027
According to new changes in kernel 5.4 version onwards, driver has to
provide the policy for a NL command to be verified against while
registering wiphy to the kernel.
To satisfy kernel 5.4 requirement add policy to following vendor
command as part of this change:
QCA_NL80211_VENDOR_SUBCMD_ACTIVE_TOS
Change-Id: I915ec5494ef16e7cc5b8c42d814c512a925ef469
CRs-Fixed: 2634120
According to new changes in kernel 5.4 version onwards, driver has to
provide the policy for a NL command to be verified against while
registering wiphy to the kernel.
To satisfy kernel 5.4 requirement add policy to following vendor
command as part of this change:
QCA_NL80211_VENDOR_SUBCMD_FETCH_BSS_TRANSITION_STATUS
Change-Id: I7c49d959e7c5d232572aae78616b18cee875cbb1
CRs-Fixed: 2632084
According to new changes in kernel 5.4 version onwards, driver has to
provide the policy for a NL command to be verified against while
registering wiphy to the kernel.
To satisfy kernel 5.4 requirement add policy to following vendor
command as part of this change:
QCA_NL80211_VENDOR_SUBCMD_NUD_STATS_SET
Change-Id: I1023872146d398252cd8dbde8431cd8c5e839a31
CRs-Fixed: 2631294
In function rrm_fill_beacon_ies, do while loop is checked
for BcnNumIes if it is greater than IE length 0. Fix the
check to be greater than 2 as the first two bytes is IE
header(element ID and IE length fields both 1 byte each.)
Change-Id: I11e5de481cd49a22acafee938fbe73f839f5b0e4
CRs-Fixed: 2626729
Remove the excess error log in hdd_rx_deliver_to_stack. The hdd
rx/tx stats are incremented in caller for success and failed
cases for delivering the skb to network stack. This error log
is redundtant as stats for rx packets refused is incremented
when packets are dropped by the network stack.
Change-Id: I5a774db18966f9b43721278daef936de7524d6f7
CRs-Fixed: 2633475
According to new changes in kernel 5.2 version onwards, driver has to
provide the policy for a NL command to be verified against while
registering wiphy to the kernel.
To satisfy kernel 5.2 requirement add policy to following vendor
command as part of this change:
QCA_NL80211_VENDOR_SUBCMD_THERMAL_CMD
Change-Id: Ia5a5e62b3fe086c3fab58d92d12898f525f774b8
CRs-Fixed: 2631242
According to new changes in kernel 5.2 version onwards, driver has to
provide the policy for a NL command to be verified against while
registering wiphy to the kernel.
To satisfy kernel 5.2 requirement, add policy to following vendor
command as part of this change:
QCA_NL80211_VENDOR_SUBCMD_ENCRYPTION_TEST
Change-Id: I37836165dc8ff89f7179d5024cc3b1516cacf6e6
CRs-Fixed: 2633303
The function hdd_softap_deregister_sta takes the sta_info as the
argument and calls hdd_sta_info_detach. In hdd_sta_info_detach, the
memory assigned to the sta_info is being freed. For this memory to be
properly freed and set to NULL, the actual memory location must be
passed to the function; which is currently not happening.
Pass the actual memory location by reference using a double pointer so
that the memory cleanup is proper.
Change-Id: If0f846957df0378ea7a13b76bdf9c6ef562ed90e
CRs-Fixed: 2627296
