For 6ghz AP with open security,the STA join req was not going through
due to security check added from CR2715086.
Fix is to move the rmf enabled check inside lim_is_6g_allowed_sec().
Change-Id: I32fb0de34fdf05063dee5f28aac164b1dfcaea5e
CRs-Fixed: 2746745
Currently mac trace msg rx function is passing module
id as a second argument to mac trace function instead of
message id.
As mac trace expects message id as an argument, pass message
id to the mac trace function as message id.
CRs-Fixed: 2719737
Change-Id: I9fa1611d6095975241a01325b798c24ea654df3e
After SAP switches the channel, policy manager needs to check if
the host needs to change HW mode. SAP state machine updates channel
change event to hdd to indicate SAP channel switch. Hence move logic
to change HW mode from start bss success event to channel change
event case in sap event callback.
Problem scenario:
1. DUT is in Single MAC mode by default.
2. SAP is up on Channel-1. So SAP is on MAC-0.
3. Host sets Policy Mgr Hw mode = DBS.
4. STA comes up on Channel-36. As host is in DBS mode, STA came up
on MAC-1.
5. SAP does CSA to Channel-36 (STA’s channel). So SAP moves from
MAC-1 to MAC-0.
6. Host sets Policy Mgr HW mode = Single MAC (As both VDEVs are on
same band).
7. Now, SAP does CSA to Channel-11. As Policy Manager Hw mode is still
Single MAC, SAP is still on MAC-0. So now STA (Channel-36) & SAP
(Channel-1) are in MAC-0 doing MCC.
Fix:
After SAP switches channel, policy manager checks and changes HW mode
change in hdd sap event callback.
Change-Id: If7964057592d85a11dd77197c889a4ed77ed039a
CRs-Fixed: 2719810
After roaming, FW updates host by roam sync indication. Host parses
the reassoc request in roam sync indication to update RSN params of
vdev crypto.
Change-Id: I9638a77150e81ea911e95d294c58d605871630a0
CRs-Fixed: 2746470
The last parameter of stop_roaming_callback is currently an
unsigned int, which does not match the function that is assigned
to this pointer, which has enum wlan_cm_rso_control_requestor.
Update the function pointer to have the correct parameter.
Change-Id: I2761293e6d87e9fcf9586d198a6e60f25ca2b51e
CRs-fixed: 2745188
Enhance BLM infra to include source,
reason for blacklist, original timeout,
received time for better debug.
Change-Id: Ia705a967a08412824063275f5073c338dabde539
CRs-Fixed: 2744402
In an IOT scenario, client is VHT capable and is carrying
VHT IE in assoc-req frame while our SAP is configured as
HT only.
Key points here are the phymode and vht_flag populated in
WMI_PEER_ASSOC_CMDID.
phymode is set with SAP's own capability taken into considertion
while vht_flag is not. This leads to FW TX data using VHT data
rates.
Fix is to properly set htCapable and vhtCapable with SAP's own
capability taken into considertion.
Change-Id: I7493e90aa744665569093d3a67714c1224d010a0
CRs-Fixed: 2740102
- Limit the timeout value of the BLM entry if it has big comeback
value and allow connection to that BSSID.
- Fix the BLM entry time stamp boundary checks.
Change-Id: I07bf7b1fce1c1e8d349c4fc0a9b0fed07f237197
CRs-Fixed: 2741689
