With below INI configuration, SAP is not following the STA
channel. It's forming STA + SAP MCC instead of Forced SCC.
1. gWlanMccToSccSwitchMode = 4
(QDF_MCC_TO_SCC_SWITCH_WITH_FAVORITE_CHANNE)
2. gEnableSAPManadatoryChanList=1
When channel switch mode is
QDF_MCC_TO_SCC_SWITCH_WITH_FAVORITE_CHANNE and if STA
is on 5ghz and SAP also comes on 5ghz then driver considers
the HW mode as DBS capable and it allows SAP to form
MCC which is not favorable.
For non_DBS target, the fix is to allow SAP to
do force SCC if the channel switch mode is
MCC_TO_SCC_SWITCH_WITH_FAVORITE_CHANNE.
Change-Id: I4b945dc1831909caff72f8398c959f4450765f2b
CRs-Fixed: 2972273
Enable config flag to skip MSI configuration for
monitor status and destination rings in MISSION
mode.
Change-Id: If295a5afc6731bbec1ad7182590e0015f3a911ba
CRs-Fixed: 2992169
Currently only default values of local edca params are used for
WME and ETSI profiles. Therefore expose them as INI config options
so that driver is able to parse user configured edca params used
locally by SAP.
Change-Id: I81759570160a67e26f68501576d71a5fd3568cd7
CRs-Fixed: 2976143
For STA+P2P concurrency case, once p2p disconnect, STA max tx power is
updated in F/W too per SAR by design, app can't correct it since reconfig
same max tx power as original is refused by driver.
Fix by not comparing cached max tx power for each vdev in driver when set
max tx power, can set same value as original again to F/W directly.
Change-Id: Ic417946006f07be40aa34f1dc022d7fb5c4aa213
CRs-Fixed: 2996316
Currently there is no synchronization for flush log completion
between fw and userspace. When host driver receives command to
flush logs, it sends the command to fw and releases the control
of the userspace thread, it does not wait for the flush log
completion event from the fw and because of which user space
does not know when the host and fw completes the log flush.
To address above issue add a logic to wait for fw event of
flush log completion before host returns control to userspace.
Change-Id: I04fa0aead146d2b7b8627e4101c6dcd99d3947e9
CRs-Fixed: 2983375
INI parameters are configured based on requirement. It is expected
that atleast one parameter should be configured through INI file.
To mandate this, trigger assert when failed to parse atleast one INI
parameter from INI file.
Change-Id: Ia94f9ae9ce91d7e57f7a6be6c6f955de5ba860a4
CRs-Fixed: 2881695
During FT-EAP roaming after session timeout if the FTIE received
in the EAPOL of full EAP is improper, the supplicant would
disconnect the AP with the reason FTIE mismatch.
During this disconnection supplicant flushes all the existing PMK
cache entries and eventually the framework would add these cache
entries again (apparently, the current entry would be with the
older PMK). On this addition to the driver, there is no connected
profile and thus no MDID is associated to this PMKSA entry(AP1-PMK1).
Further, on the fresh (Full EAP) connection to the AP2 with the
same MDID, a new cache entry gets added and thus MDID from the
connected profile gets associated with the PMKSA cache entry. At
this point of time, there are two PMKSA cache entries (AP1-PMK1
without MDID and AP2-PMK2 with MDID).
Adding further, if the incorrect PMK (without MDID / stale entry)
i.e. PMK1 is given to the firmware on the RSO command for the
specific BSSID (here AP1) during roam, further roams shall be
calculated with this PMK1 and result in to the invalid pmkid
issue.
Thus, avoid this situation by removing that stale PMKSA entry in
the driver and this entry can be deleted only when it is associated
with the MDID. Driver on the new pmksa addition shall check for the
matching pmksa cache entry with the MDID and delete the earlier ones.
To associate the MDID, this commit checks for the same from the scan
entry of the BSSID, if there is no connected profile for the same
(this happened when the framework has added the cache entry when in
the disconnected state).
Change-Id: If81d66059173dda8d7a2940ca10dc96ef16e125c
CRs-Fixed: 2972115
In wlan_hdd_get_wiphy_channel(), Donot access
60 Ghz which are not part of wiphy.
Change-Id: Ie8249bdcc7c4fb66744a9b16f2c194e9ab60dd1b
CRs-Fixed: 2984046
Enable SAE Roaming with same PMK feature INI
sae_single_pmk_feature_enabled by default.
Change-Id: I5be1b24fd77f5296574276af02b0098ac86d9730
CRs-Fixed: 2985116
Send error to userspace if ack status is not successful due to
firmware internal error
Change-Id: Id3fbbc2099fbdf597e4aebf6b532086c47a07943
CRs-Fixed: 2991060
In case if TWT command (i.e setup, terminate, pause, resume,
nudge) comes from userspace and if the firmware is in below mode
1. scan in progress
2. roam in progress
3. CSA is in progress
4. any other error
then the command needs to be rejected in userspace context
Synchronize the TWT commands so that whenever command goes from
driver to firmware, then driver will receive ack event first
followed by respective event (i.e add dialog, delete dialog,
pause, resume, nudge) with below condition
1. If driver receives the ack event as successful then driver
waits for this ack event, respective event with status of the
TWT action frame over the air is expected.
2. If driver receives the ack event as failure then it will
reject the TWT command request in userspace context.
Change-Id: Ib68b89b74b5e44f28106884efd7412cee49f5bd8
CRs-Fixed: 2987978
Add 6Ghz band HE capabilities for TDLS setup request and
setup response frames.
Change-Id: I02e8da12acc6832ad39d7166961c1c6546c8ad49
CRs-Fixed: 2994066
Add TWT service bit capability support to check whether firmware
supports ack event or not. If firmware doesn't support ack event
then service bit capability will become 0 and whenever the TWT
command comes, host will not wait for ack event and sends command
in a legacy way
This support is mainly added to handle new host and old firmware
combination.
Change-Id: I556d8edf0b505b774d756d6d904dd445418837bf
CRs-Fixed: 2987966
Add policy mgr connection list validation such as duplication
entry error. Flush the drv log and pause the logging
if error happens so that the issue log can't be overwritten
in stress test.
Change-Id: I037863de0bc5ecb8118c5792b6d73c3e200dd5c6
CRs-Fixed: 2991983
Add gConfigBleScanCoexPolicy which can be used to
control performance of ble scan case.
’0’ to place more emphasis on BLE Scan results
‘1’ to place more emphasis on WLAN performance
Change-Id: I46c735d8695523d14f6372bc5e47d1d1f51589ae
CRs-Fixed: 2935051
In hdd_sap_twt_get_session_params(), check NULL value of
params variable before it's used.
Change-Id: I47e57cbe98d7a0ee7015ab628d665037bf0b9853
CRs-Fixed: 2989510
Currently, In Reassoc and fast reassoc command host
validates freq from secondary channel list that may
cause issue for some frequencies which may be valid
for sta but invalid for sap.
Fix is to validate freq from valid channel list
Change-Id: I1ee81212425f7b4f997568b4fd92153231e349e8
CRs-Fixed: 2991541
All msdu's which are received in single mpdu will have same 802.11
header. Hardware fills header of only first msdu. So copy the
first msdu's header to all msdu's which are received in single
msdu in packet capture mode.
Change-Id: I1c9fd55e571eda77be0ab0863e03cd61b848b842
CRs-Fixed: 2968770
Fill the Coding info and STBC in HE data field of radiotap
header for TX data packets in packet capture mode.
Change-Id: I173ce1846259ee9e94587e360256161f8147df08
CRs-Fixed: 2984436
Currently, if there is no twt session present as part
of the twt get_status query with dialog_id = 0, host
returns failure.
Add support to include the session state, wake_duartion
and wake_interval for TWT get_status command with dialog_id = 0.
Change-Id: Ie59310dc07c9954da96cee6568de856be8f67652
CRs-Fixed: 2989788
Handle A-EDCA based on STA-SAP concurrency. Also, update
RTS profile based on the concurrency such that:
1) For STA and SAP concurrency, send STA's AP EDCA
params to fw. Also, for SAP or P2P Go, update the
value in Broadcast EDCA params as well so that it
should be broadcasted to other stations connected
to that BSS. Also, update the RTS profile value to
0x11. It will let FW disable SIFS bursting and send
RTS for every frame.
2) For standalone STA (can even happen after SAP/P2P Go
disconnects), if the parameters are updated, reset
them to original parameters and send them to FW.
Also, update the RTS profile value to the value
it was set before.
3) For standalone SAP (can even happen after STA
disconnects), if the parameters are updated, reset
them to original parameters and send them to FW and
reset the Broadcast EDCA params as well so that it
should be broadcasted to other stations connected
to that BSS Also, update the RTS profile value to
which it was set before.
Change-Id: Idb2b04b1b0bddb51cea9c5665847d04817a90aca
CRs-Fixed: 2949484
Fils info is stored per vdev. In RSO scan mode command, in FILS
TLV, the next ERP sequence number to be used in the next FILS
connection is sent to firmware and is filled from the vdev fils
info. But after roam sych event is received, the erp sequence
number is not updated in the vdev fils info, causing FILS roaming
failure.
Update the fils erp sequence number to vdev fils info after
roaming.
Change-Id: Ibc624d9c4b0fc535c430881d3033169b002c8419
CRs-Fixed: 2988113
According to new user request, add channel frequency 5745,
5765, 5785, 5805 to SAP mandatory channel list.
Change-Id: Icf1c96c07514f65a229e00d4330eaf0af5daa4ab
CRs-Fixed: 2987664
Some times there is delay in update of channel freq in vdev
because of which M1 channel freq is zero during initial
connection.
Fill freq from msdu start from rx_pkt_tlv.
Change-Id: Ia0a8f61c9113fbe5bc3ad932dcb67111b86629af
CRs-Fixed: 2964512
The delay before vdev stop is a global config,
no need to set for each interface separately.
Change-Id: I5760cf083a6749bb82cc88635a947f1d18308dfe
CRs-Fixed: 2904748
Currently, host sends DS param to fw based on
channel number but channel number may be same
in case of 6G and 2G due to which IEs can be
included in case of 6G which is not required.
Fix is to send DS param based on freq to
avoid addition of IEs in case of 6G band.
Change-Id: Ib711731fda3cfb0117478e6b1e026f40639a7fbb
CRs-Fixed: 2942323
