As part of 320MHz bandwidth support for 11BE, define an API
to get max supported EHT bandwidth in SME, which in turn gets
max BW from WMA layer.
Change-Id: Ifae397ec38cd89758215a9d09fe58a4d7afd22f4
CRs-Fixed: 2935861
In roam sync handling, pmksa memory is freed right after
set pmka entry is updated in crypto priv params instead
allocate separate buffer for crypto.
Change-Id: I337efcb29d2233b016f93cae7f4f23d3203786a6
CRs-Fixed: 2931162
Change I57acca2257a263225d9bafb0f94e195a99224a60 and
I7d247ae9fc83d7b578b01ec664247c807f7834fc add code in the non
connection manaeger part of the code which is not used now.
Thus move the logic in LIM for connection manager.
Change-Id: Iaa7c31ca9deb3dae9af1aa0161f0177b1b6d9f93
CRs-Fixed: 2939766
Consider two APs: AP1, AP2
Both APs configured with EAP 802.1x security mode
and OKC is enabled in both APs by default. Initially
DUT successfully associated with AP1, and generated
PMK1 by performing full EAP and added an entry for AP1
in pmk table. At this stage, pmk table has only one
entry for PMK1 (1. AP1-->PMK1).
Now DUT roams to AP2 using PMK1 (as OKC is enabled)
but session timeout happens on AP2 just before 4 way
handshake completion in FW. At this point of time DUT not
in authenticated state. Due to this DUT performs full EAP
with AP2 and generates PMK2. As there is no previous
entry of AP2 (AP2-->PMK1) in pmk table. When host gets
pmk delete command for BSSID of AP2, the BSSID match
fails. Hence host will not delete pmk entry of AP1 as well.
At this point of time, the PMK table has two entry
1. AP1-->PMK1 and 2. AP2 --> PMK2.
Ideally, if OKC is enabled then whenever timeout occurs in
a mobility domain, then the driver should clear all APs
cache entries related to that domain but as the BSSID
doesn't exist yet in the driver cache there is no way of
clearing the cache entries, without disturbing the legacy
roaming. Now security profile for both APs changed to FT-RSN.
DUT first disassociate with AP2 and successfully associated
with AP2 and perform full EAP and generates PMK3. DUT first
deletes PMK entry for AP2 and then adds a new entry for AP2.
At this point of time pmk table has two entry AP2--> PMK3
and AP1-->PMK1. Now DUT roamed to AP1 using
PMK3 but sends stale entry of AP1 (PMK1) to fw via RSO
command. This override PMK for both APs with PMK1
(as FW uses mlme session PMK for both APs in case of FT
roaming) and next time when FW try to roam to AP2 using
PMK1, AP2 rejects PMK1 (As AP2 is expecting PMK3) and
initiates full EAP with AP2, which is wrong.
Fix is to update pmk table entry for roamed AP1 with PMK3 value
comes to host via roam sync indication event.. By this host
override stale entry (if any) with the latest valid pmk for
that AP at a point of time.
Also add new api to get the sae single pmk ini value and
update the bss desc of single_pmk cap after intersecting the ini
value.
Change-Id: I12fecbae69d0d2a11f2a39eee6be960752d831bd
CRs-Fixed: 2889847
If STA Country Code is US and if AP Country IE has a different
county code, STA should not allow connection to this AP as VLP
mode is not implemented yet in the US.
If STA Country Code is GB and if AP Country IE has a different
county code, STA will use VLP mode.
Change-Id: I7d247ae9fc83d7b578b01ec664247c807f7834fc
CRs-Fixed: 2933632
Enable SAE authentication for P2P. This allows to process and
forward the SAE auth frames to userspace in P2P_CLI and
P2P_GO modes.
Change-Id: I210f6b3db4d4d0a39f1dcb7f136ec9ac7e4c34c4
CRs-Fixed: 2933379
Address below corner scenarios for dual sta roaming:
1. Initialize primary interface vdev id
with WLAN_UMAC_VDEV_ID_MAX.
2. Enable roaming while processing set primary interface
vendor command irrespective of dual sta roam policy.
3. Disable mcc_adaptive_scheduler before sending
WMI_RESMGR_ADAPTIVE_OCS_ENABLE_DISABLE_CMDID to FW and
enable it if host receives dual sta policy as unbiased.
Change-Id: I8e5254c6f9053bd5fe7f925af4b577e76c9b9a2e
CRs-Fixed: 2928870
If STA + STA connected in MCC, FW should distribute
the duty cycle between primary and secondary connection
in 70:30 ratio.
Quota for the 2nd role is calculated as 100 - quota of
first mode.
Change-Id: I36ab9a9717da1e1f0ff0e0e11a18681c97ed6c58
CRs-Fixed: 2927460
Currently below implementation is missing in the driver. So driver
is failing to associate in 11be. Add this implementation to support
11be association in the driver
- Filling EHT IEs in probe response
- Sending EHT mcs capabilities while creating the peer
- Fix compilation issues when 11BE feature is enabled
- Add the the 320MHZ to wma_chan_phy_mode
Change-Id: Ib535db413d5578840feed7fd18bb00e5e28cfb6f
CRs-Fixed: 2926471
Add logic similar to I5d8ec9e9d4f8a44178b113d370799fe2bc0373fb
in connection manager to flush PMID on HB failure.
Change-Id: Id87b5774a18a377719c56d3f34dc31284f0a39a3
CRs-Fixed: 2928282
Two new IE eht_op and eht_cap will be added for 11be.
Implement eht_op and eht_cap changes for sme layer.
Change-Id: If6d11e2cad2ff87ac82b07c7ecb9dd05ac53f0ee
CRs-Fixed: 2908058
If firmware sends the TWT teardown due to concurrent session is
established, then the wait for notify flag is not set. So other
commands can be sent to firmware.
In case of TWT teardown due to concurrency, set the wait for
notify flag.
Change-Id: Ia1d5134e1c6d931f8c5ced1c011efb3489d343ad
CRs-Fixed: 2919799
Currently, mlme_twt_is_command_in_progress() function checks if the given
command is in progress or not. For inputs like WLAN_TWT_ANY, if this function
returns true then from the current logs, its not known which
active command in progress.
Hence for better debugging, enhance this function to return active command.
Change-Id: Ibc5c5babb042408b0e8988fe229d344ed98bfff3
CRs-Fixed: 2920494
1. If the TWT setup parameter re-negotiation results in failure,
then host driver shall trigger TWT teardown for the
existing TWT session.
2. Upon receiving the TWT teardown confirmation from the firmware,
host driver shall cleanup TWT session, send teardown notification
to the user space and ready for next TWT setup command.
Change-Id: I553ae7de8d900a3dc12d563b781f9fefa36f8a0b
CRs-Fixed: 2916548
The userspace doesn't expect TWT teardown or notify events after
roaming. So to clear the driver internal TWT context, for old
peer, call the mlme_init_twt_context() on roam synch complete.
Change-Id: If1e4fe2d79561885052caf8d5231d1c943f10c96
CRs-Fixed: 2912872
The operating class triplet was removed from country IE. Add the logic
to populate it back in.
Change-Id: Ia9a1489e04d832b650dbe203534f38980e7e1506
CRs-fixed: 2913363
Fix to pass assoc_info instead of address of assoc_info
to sme_qos_csr_event_ind() and cm_remove_cmd()
Change-Id: I9f6c12870954c42f2b1e6250e7547c45a593cae8
CRs-Fixed: 2911027
BSS max idle testbed test requires to prevent the data and
manamenet response frame Tx with user configuration.
Add support to prevent data Tx and drop Rx mgmt frames so that
response frames is not sent.
Change-Id: I01f08fd8f30dc4b1b80801434918b976abb09e3c
CRs-Fixed: 2817703
Add change to support roam ho fail and roam invoke fail
indication in connection manager.
Change-Id: I8e4fed2ca4b9c6e95da86b0c37e39da8f2bc4953
CRs-Fixed: 2906319
Supported rates and extended supported rates together checked
against max supported rates that is failing the processing.
Fix the value to check against the max rates.
Change-Id: I3a20c5ac496fbedda5b105d95a1af9a168a53864
CRs-Fixed: 2895899
Firmware sends TWT teardown with status code
WMI_DEL_TWT_STATUS_CONCURRENT_SESSION when a concurrent connection
is established. Currently host driver drops this event as the
status code is not WMI_DEL_TWT_STATUS_ROAMING_INITIATED or
WMI_DEL_TWT_STATUS_PEER_INITIATED.
Add support to handle TWT teardown event with
WMI_DEL_TWT_STATUS_CONCURRENT_SESSION status code.
Change-Id: I408ba960924b4daa1ca4f8337d7e0d1ce52c5fd9
CRs-Fixed: 2899563
Remove all of the conditional compilation for pmf since this
feature is mandatory for future scope from protocol point
of view.
Change-Id: Id3a2127e9ecb343ad2a0354dcbc331c22167d7fb
CRs-Fixed: 2852630
Currently, In twt setup command, driver set the
TWT command_in_progress before adding the dialog_id
in TWT context. Due to which, set active command
fails because the dialog id was not added to the
twt context. So the add dialog command response is
getting dropped at sme.
Set the TWT command_in_progress after adding the
dialog_id to TWT context.
Change-Id: Ic2c7e23720e2bc9f5a6737ba2f1dc4b1356dc179
CRs-Fixed: 2897736
Add support to configure the HE ER SU for management frame tx
and configuration support to use RU 242 tone for data Tx.
Change-Id: I068c1e7b6808d430d5468bab7ee04e24d5461afd
CRs-Fixed: 2816797
This change removes unused variable "mac" in function -
sme_set_auto_shutdown_timer and avoid compilation fail.
Change-Id: I4a3ae1ea0deb62d6d43845330162dc8a24b8ab62
CRs-Fixed: 2890806
Move prev ap info and connected bss in connection manager
macro in csr session.
Change-Id: Ie2b8ecdbcf7134f93f908ba596c0398712da7ac8
CRs-Fixed: 2895259
Fill operational and extended rates in LIM
instead of CSR as part of connection manager.
Change-Id: I9197e835703059d61bc67897a9670ff166460318
CRs-Fixed: 2892415
Currently, in TWT after posting the msg via sme to WMA
using scheduler thread. Based on the success or failure
driver set the command_in_progress so that subsequent
commands can be rejected till the current command is completed.
There is a chance, context might be broken because of this,
command_in_progress is not set.
Set the command_in_progress before posting
the msg and if there is an error then again set the
command_in_progress as NONE.
Change-Id: If9dc4bd346178d49d5d940ecf8ae008969cb1e73
CRs-Fixed: 2886135
In scenario, when ROAM HO failure is piggybacked on WOW wake up,
the blm reject AP addition fails as mutex can't be acquired in
interrupt context. With this change, the reject bssid blm
addition will happen after changing context to scheduler thread.
Change-Id: I685501b7ea48e4461922a7a50fb39c52d4d607f3
CRs-Fixed: 2880712
When CSR issues a start BSS message, it validates the requested start
freq against the internal CSR channel list. There could be a scenario
where this list is not updated and the validation fails. Check this freq
against the regulatory channel list instead.
Change-Id: I56b29fa6249a9245bb968c95c14e730b976f0f8d
CRs-fixed: 2884695
As chan num may be same for different bands, getting chan state
from channel number may provide incorrect chan state.
Fix is to get chan state from frequency instead of channel number.
Change-Id: Iaf379614d8e536dba2cde71b9294a5a4b018769a
CRs-Fixed: 2869828
Update the logic to fix a potential memory leak when there is an
invalid country IE. Also update the logic to not reject the connection
in the case of an invalid country IE, since this is a bad user
experience.
Change-Id: I6a2b50a483e65554a6622dccbb0bac61331fc4fb
CRs-fixed: 2883385
