ssid_allowed_list is cleared for each RSO stop.
To fix it, only clear ssid_allowed_list when disconnect, don't clear
it for each RSO stop.
Change-Id: I577191295d388ab92440d7bf65b6a0da6c342181
CRs-Fixed: 3087296
when MLO is enabled the non-mlo connect notification are not getting
sent to the userspace in case of security association resulting in
the assoc timeout.
Send the connect notification in the SAP side and also release
the peer reference cleanly.
Change-Id: Id0f190be547c03f26c59a49cb8c4a74e1b90877c
CRs-Fixed: 3085979
If MLO STA is present, allow further STA connections to all
available bands/channels irrespective of existing STA
connection band.
Change-Id: Ic7da10b2e74645b73c579b38f43bb7e3105b6f55
CRs-Fixed: 3088656
Support to deliver SMPS, OPMODE to user app, and
deliver RRM report to son module.
Change-Id: I9e12043e59878c5e46d24f02717356ad40d7e35d
CRs-Fixed: 3056538
Use wlan_get_vendor_ie_ptr_from_oui() instead of
wlan_get_ext_ie_ptr_from_ext_id() to parse vendor specific
WFA Hotspot-2.0 IE
Change-Id: Ie9ee6c1f16d0eb83f52b7d9afa97f362f8400ff3
CRs-Fixed: 3080931
When connect from wpa_supplicant and roam from F/W happens at same
time, supplicant hold cm cm_req_lock and wait rsp from scheduler
thread, sheduler thread is blocked to wait for cm_req_lock.
Change-Id: I6b9010972d29be9a32d3b85ee72891ed62b50801
CRs-Fixed: 3087169
Add numss_m1 and ru_bit_mask check before access the data in
ppet16_ppet8_ru3_ru0.
numss_m1 + 1 should not exceed WMI_HOST_MAX_NUM_SS.
ru count should not exceed 4.
Change-Id: Ide6b562dacb0592fb5c2101c0ce016570cb1dac3
CRs-Fixed: 3080599
Bus bandwidth timer tweaks certain aspects of the system during
throughput transitions. For example, when throughput goes high, system
parameters are tweaked in favor of system performance. Hence, when high
performance is not needed, the timer relies on throughput transitioning
to low to reset the parameters in favor of power.
During a corner case, its possible that while througput is high, wlan
adapter is immediately brought down. This stops the bus bandwidth timer
abruptly without letting the the timer detect a throughput transition to
low. This may result in higher power consumption even when there is no
data activity or throughput is low.
Explicilty force a transition to "IDLE" state when bus bandwidth timer
is stopped.
Change-Id: I0a0a64a855714b1a8b5a52a048604fef54a0ee41
CRs-Fixed: 3087118
There is a race condition when adapter is deleted after it is
validated in DP rx path and is assigned an invalid vdev id and
eventually invalid net_device.
To fix this, dropping packets if vdev id is found to be invalid
right before assignment to skb->cb.
Change-Id: I4e483363f59a22b45e18da929f749cd9807cc2fc
CRs-Fixed: 3084556
"sap_radar_found_status" is used to check Radar event detected
or not in CAC wait state. Clear "sap_radar_found_status" before
SAP starts to avoid the stale value saved in previous sap start or
CSA. This can happen when the SAP is restart state and get
"stop ap" request from userspace. The invalid value will
cause the wlansap_start_beacon_req retrun without deliver start
beacon msg and cause the no beacon in OTA.
Change-Id: I6336510881333e2775c29dcc167a77d5d745ace9
CRs-Fixed: 3085312
Function lim_update_sta_run_time_ht_switch_chnl_params() will check
preauth condition, but it is not enough, as preauth will create a
new session with pe session with same vdev_id.
It should work in preauth condition, but not after preauth is done.
Replace the checking by function wlan_cm_is_vdev_roaming(). And
remove following lim_is_roam_synch_in_progress checking, as
wlan_cm_is_vdev_roaming checking already cover LFR2 and LFR3 both.
Change-Id: I06732ac7fdc98fe8eba438c4be50861ce8debe08
CRs-Fixed: 3080663
Currently, SAP state machine is moved to INIT state when SAP
start is aborted due to timeout or SSR. SAP is not cleaned up
in such cases as eWNI_SME_STOP_BSS_REQ (which further issues
vdev down and cleanup the peers properly) is not sent to
below layers(firmware).
Replace qdf_wait_for_event_completion to
wait_for_completion_timeout in start_bss which will wait
till the normal operation execute irrespective of firmware
state/SSR.
Change-Id: Ifff2ca9658769cb1145f1c5cb278cd7551cb8c00
CRs-Fixed: 3058550
During SAE roam auth offload, update the beacon/probe response
frame coming from the FW via WMI_ROAM_FRAME_EVENTID into the
scan db.
When the bss info of the preauth candidate is unavailable in
the host/kernel scan entry, supplicant fails to determine the
proper SAE PWE config of the peer and the commit request fails.
Change-Id: Ia782ece7bebf8274f949fe9fb3b2a2882bf47597
CRs-Fixed: 3075458
Currently, ping latency enhancement feature only supports IPv4, if
a ICMPv4 request frame is recevied during a configurable interval,
it will be marked to route to FW. This change extends to ICMPv6
request frame as well.
Change-Id: Iefa563bc1788c233c5f6a0dbb1a586d163b16284
CRs-Fixed: 3082398
Currently sched-delay is not taken into account while calculating TX/RX
offload packets in bus bandwidth work handler. This may result in an
incorrect calculation and determination of TX/RX bandwidth levels and
other params which are derived from it.
Add support to consider actual scheduling delay between two bandwidth
intervals to detemine TX/RX offloaded/not-offloaded packets.
Change-Id: Icfb961cbbc1a049df0133394883755418b631056
CRs-Fixed: 3079953
REO interrupt is fired after sending WOW_ENABLE command
to FW. Multicast packets are processed and dp_tx_send is
invoked as part of intrabss forwarding. This results in
a FW exception.
Fix is to disable intrabss forwarding on SAP/P2P GO
on system suspend and enable it back on system resume.
Change-Id: If9f20bf59b776016dac3c1a27200deafa80266b5
CRs-Fixed: 3084288
Currently, in TWT setup command, if peer does not support TWT
capabilities then firmware returns status = 4.
Add condition to check the peer capabilities before sends TWT
setup request to firmware.
Change-Id: Icd1cbeff2db2bdec4e456013e98270a526ff22ce
CRs-Fixed: 3082071
For ML STA + Legacy STA case, FW asserts due to legacy STA shares
the same MLD address with MLO STA.
Change-Id: Ibd8045007bd7c120dee7b1e8f7faccc0a80cea0b
CRs-Fixed: 3063367
Revert the DBS ultra high TPUT Max voting. Max voting is not required.
Instead vote for ultra high bw vote.
Change-Id: Ic8ee47a0c8422be5590d2a009b4700b4a3a8124a
CRs-Fixed: 3078684
Currently, NDP peer multicast address is derived from peer MAC address
and cached in the host. While removing the NDP peer, peer MAC address
is used to search the cached multicast address list. Because of this,
peer multicast address list is not getting freed.
To resolve this, derive peer multicast address from the peer MAC address
while clearing the cached multicast address list.
Since MAX NDP sessions are 8, allocate memory for peer multicast address
list during the NAN vdev private object allocation. This avoids the
special handling for peer multicast list in multiple error scenarios.
Change-Id: Ifbf890a4b9c8be54d84a5b57ed8f6c237ecd51ca
CRs-Fixed: 3085069
The driver sends BMISS disconnection logging event when firmware
sends the bmiss event to host. But if the AP responds after
sending the unicast probe request then we stay connected to
same AP. This could cause the BMISS disconnection log sent
earlier to be a false alarm.
Send the BMISS disconnection logging event only when host driver
initiates teardown with the AP.
Change-Id: I021b335071f803829bdc55249f1071ceaa92edc9
CRs-Fixed: 3083568
Currently memory allocated for structure roam_pmkid_req_event
is freed in two places causing usage after free.
Fix is to free memory only once in
target_if_pmkid_request_event_handler api.
Change-Id: Idc70e8437f89cb1cf4f6d35f924085409994714a
CRs-Fixed: 3064667
Enable TX AST index search for HMT STA which is more efficient
compared with older source address search.
Change-Id: Ie5ebf4199ada959ebd33351929cf642c21657c51
CRs-Fixed: 3084026
Some IoT AP set maximum transmit power as 4 in transmit power envelope
element IE, which violated wifi 802.11 spec: 9.4.2.161 Table 9-276,
DUT STA didn't handle the exception case, accessed index 7 of array
with length 4: get_next_higher_bw[4], out of bound happened.
To fix it, add code to handle the exception case that maximum transmit
power of ref AP is larger than 3.
Change-Id: Ib12062d03920b04f03de16682361e8d9e7126031
CRs-Fixed: 3083034
To support QCN7605 DBS chip, which has 3 RF chains, chain0 is for 2G,
chain1 is for 2G/5G, and chain2 for 5G. So it need 3 bits to
indicate RF chainmask for DBS mode. This is to extend the value
range for 2g/5g chainmask setting for QCN7605 DBS mode.
Change-Id: I43ee3393c121b6e9609223af1db0059158d44078
CRs-Fixed: 2933722
