Add PLD API support for mapping and unmapping memory
regions via platform driver API calls to Audio SMMU
context bank.
Change-Id: I93b5308ce6cb024773a780c0aaf98a4fd06281d7
CRs-Fixed: 3351568
The dscp value in the Qos map set element of assoc response
frame may be malformed. When try to update the dscpmampping,
make sure the value is less than SME_QOS_WMM_UP_MAX.
Change-Id: I669c5bec66a7dc839d2b2bdfa4eaafb8d7c8736a
CRs-Fixed: 3354319
Handle the possibility of NULL value for VDEV MLME component in
lim_get_self_dot11_mode().
Change-Id: I43ba34f0f1de53961c0f3ad2e675ddae899360d8
CRs-Fixed: 3356646
For GTK offload functionality, currently only 16bytes of
KEK and KCK are being copied from the userspace.
In latest kernel, kek length and kck length are sent to the
host driver as part of set_rekey_data command. Therefore,
use this length to copy the kek, kck params in host driver.
Change-Id: Idef0247aaab22022a84898eca6eb2f010ca1bf1f
CRs-Fixed: 3345506
In WoW mode, roam auth event may comes before roam start event, so CM
isn't in ROAMING state at that time, can't assume ROAMING state.
Change-Id: Ibf868db1ca0f9863d4beae4c83227cf04fe55adb
CRs-Fixed: 3357115
In wow_get_wmi_eventid(), the reason to event id mapping fills
the wrong command id (WMI_ROAM_PREAUTH_STATUS_CMDID) instead of
the event WMI_ROAM_PREAUTH_START_EVENTID and.
Since the event WMI_ROAM_PREAUTH_START_EVENTID will not be
piggybacked, remove the reason WOW_ROAM_PREAUTH_START_EVENT from
wow_get_wmi_eventid api. Fix the documentation of setting the
WOW_ROAM_PREAUTH_START_EVENT bit in pmo wow bitmap.
Fix invalid event id mapping for WMI_TDLS_PEER_EVENTID also in
wow_get_wmi_eventid().
Change-Id: Ifd08dc94cda22d9de662ef15b74cb19571007052
CRs-Fixed: 3355578
GO on 5 GHz channel 48, MLO STA 5 GHz (48) + 6 GHz (1) is UP.
SAP starts ACS, and before ACS complete, supplicant moves GO
to 5 GHz channel 149. Before GO CSA is completed, SAP ACS
is completed and start AP on 5 GHz channel 157. Then 3 home channels
are on same 5 GHz high band.
Fix by make User CSA as sync call and after GO CSA is completed
SAP should force SCC to low band during SAP starting, then avoid
3 home channels on high band.
Change-Id: I55ee559b47f270322ac3d2da7304dc5e8e104cf1
CRs-Fixed: 3352096
For SAE-EXT-KEY AKM with group-21 pwe, the PMK
length is 64bytes. Therefore, increase the max
size of the PMK to 64bytes in host to facilitate
PMK storage and PMK offloads.
Change-Id: I777a31acd56073d6a0312c47d95fe7d155b06fc6
CRs-Fixed: 3353102
In hdd_adapter structure, the qdf_session_open_event is
a declared as event type which is initialized but not used.
Remove this unused event variable and all its references.
Change-Id: Iec1ece36153a3c9986195bbc2cc19bf8a469f2ee
CRs-Fixed: 3354149
The kernel-doc script identified some documentation issues in
wlan_dp_priv.h, so fix them.
Change-Id: I38bc7293d4ef7b34bbc40930b2c1e4daaff4a13b
CRs-Fixed: 3352263
Currently host driver does not update dot11 mode info correctly
for getbssinfo command if the dot11 mode is 11AX or 11BE.
With this fix add a logic to update the dot11 mode info
correctly in response to the getbssinfo command.
Change-Id: I9ebec3ab43fe4cff1cab5f646bcc93a8c6654fd0
CRs-Fixed: 3353630
While doing CAC for moving SAP to DFS channel, channel
avoid event can be received. While in CAC is going on,
the current sap channel is not updated and remains the
channel on which sap was before CAC. It is only updated
after CSA. So, when channel avoid event is received,
it is checked against the previous frequency and hence,
no action is taken as the previous frequency is part of
safe channel. This results in sap starting and remaining
in Unsafe channel.
As, a fix when sap starts after CSA, check for unsafe
channel and if the sap frequency is unsafe then restart
it to another channel.
Change-Id: I910b80fe87fc149f25e84383b128a5e5c9d269e4
CRs-Fixed: 3287239
Driver adds a BSSID to the reject list due to multiple
DE authentication triggers from associated AP. If DUT tries the
FASTREASSOC command for the same BSSID multiple times, the host
triggers disconnection to handle roaming failure, and this results
in DUT losing the current connection.
To keep the current connection DUT should not trigger a roaming
event if the BSSID is already added to the reject list in the
host.
The fix is to add logic to avoid the FASTREASSOC trigger command
for AP(s) present in the reject list of HOST.
Change-Id: I315da12b3f93d5d9d67396a5dd9e12fa2be5fda0
CRs-Fixed: 3328847
Add channel tx max power factor to existing ACS channel weight logic,
so if AFC available can automatically select Standard Power channel
which has higher 6 GHz tx power and better performance.
Add SAP best channel selection callback when AFC triggered DCS,
DCS module will invoke this callback and dynamic switch to best
channel/bandwidth if possible.
Change-Id: I300057c2b11d0b818f4e20ba51d6ab9b82f6a3ff
CRs-Fixed: 3204199
When roam from legacy to MLO AP, vdev1 pe session is created, but encrypt
type isn't filled, so encrypt type in session and beacon mismatch,
disconnect will happen later.
change-Id: I289f81ab9b73f0d01c1c36a002f15eb2de66a334
CRs-Fixed: 3351876
If SAP switch to 6 GHz channel with CSA, its channel tx power may
change like by AFC updating, so need update TPC command after CSA
complete.
Current 6 GHz channel power is got from regdb power limit, didn't
consider AFC event to update SP channel power and state. So need
to get channel power from secondary channel list which update by
AFC data.
Change-Id: I4517dd112fa6a97d5771b3d88a2587a7ae3cd4a5
CRs-Fixed: 3204221
During the roam scan, if there are no desired APs found in the partial
frequency list, an immediate full scan on all the supported frequencies
is initiated as a fallback. This would include the 6 GHz PSC
frequencies by default.
This attribute allow that behavior to be modified to include PSCs only
if 6 GHz use has been detected in the environment.
Change-Id: I6dc380419f14b920737fd87cd9a487c28364563b
CRs-Fixed: 3351697
In the current driver implementation, host honors LL_STATS request
even in disconnected state. But in disconnected state, the ll_stats
request pending flag is not updated properly, which results in allowing
multiple LL_STATS requests being sent to FW. So, to avoid this issue,
update the flag properly.
Change-Id: I318455492dc69bd540044b593a405eacdf185ff1
CRs-Fixed: 3339867
Handle the possibility of NULL value for VDEV
MLME component in csr_get_vdev_dot11_mode() API.
Change-Id: Ib998514788466ce390d429703c6f72197597c743
CRs-Fixed: 3354425
When vdev_mac_entry is NULL, update the hw mode index as well
to avoid mismatch between host and target.
Change-Id: I67bd91af8c72dcc468c128e266e7074308de04c0
CRs-Fixed: 3342565
The kernel-doc script identified several documentation issues in
components/coap, so fix them.
Change-Id: Iec06bb65071e4d9b1ee8787da84e66ba4ffb0028
CRs-Fixed: 3352334
Host/fw doesn't support the ml peers or legacy peers with same
mac address, So reject the client with the same link address or
mld address as one of the ml or legacy peers in the system.
Change-Id: I5f625e06c1f3832739d0424e1567a9957037fef8
CRs-Fixed: 3344809
Adds support to parse and validate T2LM IE,
based on tid to link mapping pick the
association link for MLO connection.
Change-Id: I8ea23ff10f2a637148686f1e2194fd8cc1f4fb90
CRs-Fixed: 3344675
P2P OTA rx frame indications are logged in info level.
This causes excessive logs to kernel logging when peer
sends multiple frames back to back. Rate limit the logs
to avoid excessive logs to kernel logging.
Change-Id: Ia97aef1490b8dbb759c27ba60c48c93ad7831497
CRs-Fixed: 3352880
