FISA debug macro is leading to unnecessary additional functional calls,
to avoid this cleaning up macro and pointing to nop when disabled.
Change-Id: I21ebd64f61e2c31736d55e2d17f588dbddbc15c7
CRs-Fixed: 2869361
stack frame size of lim_process_auth_frame_no_session()
is more than the default limit of 1024 bytes, so reduce
stack frame size by allocating dynamic memory to
tSirMacAuthFrameBody.
Change-Id: I37bd23e1d5814950d9c1912a40058666e3de264f
CRs-Fixed: 2844332
Per Change-Id: Ifac93fb869553d0f9eb553d5c41da43c8b014ad8, it
saves the latency level and reconfig it to fw after vdev
creates. But if user is doing WiFi OFF/ON, it expects the
default wlm level to set to fw.
Change-Id: I329ad90e09a39d461c52c614d9b7a5e23d9540dd
CRs-Fixed: 2873595
Currently, driver doesn't print STA info before passing it to the
kernel. This is making difficult to debug the STA disconnection
issues.
To address this, print sta info before giving to the kernel.
Change-Id: I8346bc489bfa3ca88b307fcb8d5cd4691ca8fe0d
CRs-Fixed: 2791922
Fisa flow entry napi id is initialized to invalid value,
which will cause out of bound access during fisa flush by vdev id.
Fix this by validating array index before access.
Change-Id: Ic7b1b1448194b75777f9dc392043275235caa7f7
CRs-Fixed: 2873033
According to new requirement, when SAP manadatory channel list
enabled (gWlanMccToSccSwitchMode = 4,
gEnableSAPManadatoryChanList=1), the SAP will only be started on
PSC and VLP channels on 6Ghz band. Add all 6GHz PSC & VLP channels
to SAP mandatory list.
Change-Id: I00514c0af9c1cc07460120c928ced652aa2e8d4e
CRs-Fixed: 2870590
Host uses "oem_6g_support_disable" INI value to configure
oem_6g_support_disable of wifi pos priv psoc object. If the Reg
domain doesn't support 6Ghz band and INI "oem_6g_support_disable"
value is 0, then host enables support for 6Ghz. Thus OEM apps
supporting 6Ghz fails to get 6Ghz channel information from host.
Hence use reg domain 6Ghz support and "oem_6g_support_disable"
INI value to update oem_6g_support_disable of wifi pos priv psoc
object.
Change-Id: Id5e5b6220f3ce880da3c40aa959887ebc6bbfa7c
CRs-Fixed: 2870971
Currently when TWT commands are sent to firmware, the host driver
doesn't acquire wake lock. So the wlan can got to wow mode before
receiving the TWT command response and the response will get
dropped since host is in wow mode.
To avoid this make the TWT events as wakeable so firmware can
wake up host if host is suspended.
Change-Id: I2750049f9173de564e24114731d3fdd8ec8d6d86
CRs-Fixed: 2869865
Add WMI service FW capability check before enabling D0 and D3
WoW for SAP and GO clients connected mode.
Change-Id: I878e4ee33807804e049bf1e8b8078d28fc1d4834
CRs-Fixed: 2869072
Zero initialization of Napi id can cause napi id zero context to flush
flow that are uninitialized. Which may cause a race condition if some
other napi context is using the uninitialized fisa flow entry during the
flow learning phase.
Change-Id: Iedca4ee112efa29c70a632c4a365e95f71e8f506
CRs-Fixed: 2864633
issue step:
1 first connect with mcs_12_13 supported ap
2 switch to connect with non support mcs_12_13 ap
the linkspeed for 2nd ap will be wrong as it is leverage
1st ap's sta info in vdev_mlme_obj.
Fix is reinit mcs_12_13 in vdev_mlme_obj for each connection.
no matter if it is 11ax AP.
Change-Id: I7f6ceb2543be1df324f57183758872e6d807d8f9
CRs-Fixed: 2868617
Some of the members in pld_soc_info structure is not assigned by
platform API's. To avoid uninitialized value access by calling
function initialize pld_soc_info to default value.
Change-Id: I4b6816bf72ebb518b1b8af529763c2f8a8edb38d
CRs-Fixed: 2858219
Update the channel info in the tx_status from policy manager for
packet capture mode.
Change-Id: Id237a0ee3d102b60c2cd9d47f2febb4538f29e2f
CRs-Fixed: 2869411
Add user controlled rx addba request reject for peer AP based
on ini configuration.
Change-Id: I80a4b78c1af77f5bfa68be3163f9e9a78cc64245
CRs-fixed: 2835511
Decouple BW monitor from WDI3_STATS_UPDATE and add as a
separate feature flag WDI3_STATS_BW_MONITOR.
Change-Id: I77fb5658d995daceaada6a7d64f669da706ead9c
CRs-Fixed: 2868582
User uses SETROAMMODE command to enable/disable Legacy Fast Roaming.
Host processes SETROAMMODE and sets ini config value as per user
request and doesn't update RSO state in driver and doesn't update
RSO state change to FW. Due to this, runtime LFR config doesn't
take effect in FW and host RSO state machine.
Hence update RSO state in host and FW while processing SETROAMMODE
command.
Change-Id: I73d865468e5538566f1e0d0240d77916eb445440
CRs-Fixed: 2867697
Currently the reference count variable used to detect the net device
reference leaks is not atomic. Because of this, the reference count
updation may not be reliable in multi thread scenario.
To address this, make the net_dev_hold_ref_count increment and
decrement as atomic.
Change-Id: Ifa87177164e87880d0c6d71fb40ca03a3919519e
CRs-Fixed: 2868029
The sequence of roam states info print depends on
the sequence of Tlvs coming via WMI_ROAM_STATS_EVENTID
event.
FW does not send roam trigger, roam scan and btm rsp
info to HOST in case of new host and old FW combo.
This results in 11v info print miss in kmsg log.
Fix is to print tlvs info in a proper sequence.
Change-Id: Ic51ceebcbf3846231c2181b0a4a92d59faaaaaff
CRs-Fixed: 2841325
The event WMI_ROAM_STATS_EVENTID is received after
every roam, once the roam synch complete is sent by the host.
This event contains details regarding the roam RSSI TH reset.
This helps in debugging/understanding the scenario when roam
failure happens.
Print the info received related to roam RSSI TH reset into kmsg.
Change-Id: Ibee9fc6e9220511d6679efb24080c79bcd807ab8
CRs-Fixed: 2826321
Host needs to send down sap and go client connected mode d3 wow
feature support and hence save the default config which will be
send later down to FW via WMI INIT CMD.
Change-Id: I71ff3155e30ea03c63045473ad256dc14026f5fd
CRs-Fixed: 2866617
AEAD decryption failure happens when AP sends association
rejection frame as part of the PMF SA query procedure. AP
doesn't include FILS Session IE, but STA tries to AEAD decrypt
the frame starting from the FILS session IE and drops the
association rejection frame due to AEAD decryption frame.
So association failure timeout kicks in and proper reason
code is not indicated to userspace due to which automatic
connection retry to the AP doesn't happen.
Skip AEAD decryption if status code is not success in the
association response frame and proceed to parse the frame.
Change-Id: I9dcc85afb896717cfd20102c219b58e0e982f340
CRs-Fixed: 2797416
Update the session he capabilities when SAP switches to new
channel and if new channel band or channel width is different from
current session channel info.
Change-Id: I1a91864eb6f26189c37b2dc715e6b6d7fb950458
CRs-Fixed: 2863366
with recent commit 203218df88e7
("qcacld-3.0: Set sme power stats response cb and context to NULL")
fix in the error condition the sme global lock is not getting released
resulting in the mc thread being struck.
Release the sme global lock in the error condition.
Change-Id: I6235a632c6b74c48374d4584eb727bf9ffe296a8
CRs-Fixed: 2867358
When SAP operated in channel 36 with 160Mhz, the primary channel
36 is non-dfs and existing checking dfs will drop the radar event
if the radar detected on channel 52. Change policy mgr API to
check the dfs flags instead of primary channel state.
Change-Id: Ie2f242182b8df30e5d1875e278c5ebffa2e7cafd
CRs-Fixed: 2865173
