Add "gEnableUpdateScramSeed" ini support to send
WMI_PDEV_PARAM_EN_UPDATE_SCRAM_SEED command to firmware
to enable OFDM scrambler seed.
Change-Id: Ie5c244a7ea418eec0af1f576e8521804ee85a665
CRs-Fixed: 3106348
When the modules are closed and thermal mitigation level of the system
is not honored by the wlan subsystem. So, during the wifi restart
query the thermal level of the system and configure the same to the
firmware.
Change-Id: I9edf4748475b85fe094c68ae067d81f578ccb40f
CRs-Fixed: 3101901
Currently, host allow maximum 3 concurrent connection.
Change the maximum concurrent connection to 4 to allow
MLO STA + NAN + NDP combination.
Change-Id: I82b8b018488f2f85e4d5431b8b23b1dd90a844b9
CRs-Fixed: 3119918
Check MLO STA + NAN + NDP concurrency support. Allow this
combination only If service cap and mlo sta presents.
Change-Id: I6fd0cae227eb8c4096444160b2450ad65dc51c30
CRs-Fixed: 3120645
WLAN Host timeout waiting for resume event from FW seems to
happen due to race condition between psoc idle shutdown and
runtime resume. So, to avoid that, add runtime sync resume
before calling the pld_idle_shutdown.
Change-Id: Ie4734e66e4cc887681262b596aa2e1c400aa6e43
CRs-Fixed: 3091738
Currently wlan_cfg80211_mc_cp_stats.h file is present at
qca-wifi-host-cmn/cmn/os_if/linux/cp_stats/inc.
With this change, move file to qcacld-3.0/os_if/cp_stats/inc
as this file contain MCC specific code.
Change-Id: Ia531094fb15ae86f5afab2b9c3bdde197feaac6c
CRs-Fixed: 3108266
Currently, wma_add_sta status is not considered while voting for
link up in case of NDI. But if wma_add_sta fails to add a peer,
this link vote leads to stale link vote up.
Same is the case for wma_delete_sta and the return status is not
considered. This leads to a vote down of link for a non-existing
peer if peer is not present.
Below scenario leads to this situation,
1. Enable NAN and have an NDP connection between two devices.
2. Try to establish another NDP between the same devices but
don't respond for the request on the responder side.
3. NDP timeout happens in firmware and firmware sends an
NDP CONFIRM failure with timeout reason. This event carries
number of NDP-peers on the peer also and firmware sends
this as 0.
4. Driver removes the peer entry as firmware mentioned
no.of peers left as 0. It shall vote down the link also.
5. Firmware sends NDP_END for the first NDP connection and host
tries to delete the peer entry as part of this. But the peer
got deleted @step-4 already and wma_delete_sta returns a
failure now.
As the peer is not present, corresponding link vote-down also
should be skipped.
To avoid these, consider the return status of wma_add_sta for
link vote up and consider the return status of wma_delete_sta for
link vote down.
Change-Id: Iea40961366307f57b4f969245c0732d685d5e415
CRs-Fixed: 3108455
During legacy to mlo roaming,lim join req memory
is malloced and new pe session is created for
link vdev. In success case, pe_roam_sync_callback(),
deletes the old pe session and lim_join_req
memory will be freed.
In lim_cm_fill_link_session() free lim_join_req
only in case of failures.
Change-Id: I1b156a0dd778880c3a9664fa333d34eb18afcee1
CRs-Fixed: 3121153
Add support for below EasyMesh specific commands
1. To set user specified channels in the acs channel list
2. To trigger ACS
3. To get the ACS report
Change-Id: I1090b9a86d62eddc9954b70835c7496e5a614757
CRs-Fixed: 3080222
MLO roam sync happens first for link vdevs and then for sta vdev.
Update roam_sync-complete data to other modules(if_mgr, osif,
TDLS, P2P, firmware,..) only for sta vdev. Skip the same for all
link vdevs.
Change-Id: Ib01c7cd8d9c0bd0e7b4b48914576410aea6baa5c
CRs-Fixed: 3104553
Currently, roaming is not aborted in failure cases on
the link vdev and it's aborted only on primary vdev.
It results in link vdev not being cleaned up when roaming
fails due to some reason.
Change-Id: I0eb4b1da06a295935ff95be38228a5cacf127a73
CRs-Fixed: 3096648
Host driver creates two vdev as part of initial connection.
If the connected AP supports MLO, both(sta and link) of the vdevs
would be moved to UP state.
Firmware sends roam sync indication to host when it roams to a
new AP. The event carries new AP info and the new AP could be
legacy AP. If the current AP is MLO and new(roamed) AP is non-MLO
AP, move the link vdev state to INIT as it's in UP state.
Change-Id: Idd9638ea446306b0309e5127f08e3dbc1ec9edc2
CRs-Fixed: 3106038
Send correct tx_chain/rx_chain value to hdd_populate_vdev_chains
in hdd_set_dynamic_antenna_mode.
Change-Id: I836e70e989024be49d0bceadc0497368e87e3901
CRs-Fixed: 3118832
Currently inside wlan_cfg80211_mc_infra_cp_free_bmiss_stats
memfree of cp_stats along with bmiss_cp_stats is present,
again after the wlan_cfg80211_mc_infra_cp_free_bmiss_stats
function repeated memfree of cp_stats is present
Remove cp_stats free from wlan_cfg80211_mc_infra_cp_free_bmiss_stats
function.
Change-Id: I306e06455ef1ac92043ee8412cf1cecd01e9dfbb
CRs-Fixed: 3115379
FW can send more than one wmi_roam_sync_frame_event_id before
roam sync event,change done in host code to handle this scenario.
Change-Id: I1ab02ed3e984948b8e57a2f9a2000b9f9493629c
CRs-Fixed: 3116569
TWT initialisation will fail for each non 11ax connection
so an error log is not needed if peer object for TWT is not found.
Also, RIC data is not mandatory in FT session, so if its not
present, log a debug level print instead of error level.
Change-Id: I7fec9f88aa68b2ae947e34a1aede311e9fed2d05
CRs-Fixed: 3117535
Add and export os_if APIs to trigger object creation and deletion.
SON module will invoke these APIs during load/unload.
Change-Id: I1fe6ab335862b2b67affc5201ac6eae972b0a863
CRs-Fixed: 3104096
This change is to update sap interface restriction mask
enum check to NL80211_IFTYPE_AP bit mask.
Change-Id: If5a6748425502b1f27654a2e6bfa0e5c2b8554de
CRs-Fixed: 3118953
Extend gStaPrefer80MHzOver160MHz ini to limit STA connection in
80MHz BW for HE/VHT mode. In case of XR use-case, higher
throughput is not needed but higher reliability is expected.
This ini helps in XR glass device to always connects in 80MHz.
Change-Id: Icefd2d54214351c04dd7420269c308cec2b5ae31
CRs-Fixed: 3117216
In case of PNO scan, If firmware supports
WMI_SERVICE_PNO_SCAN_CONFIG_PER_CHANNEL, it uses the
upper-12 bits(bit-20 to bit 32) of channel_list for
flags and lower 20-bits(bit-0 to bit-19) for frequency.
If firmware doesn't support it, then channel_list holds
the frequency value only.
Fix is to fill the flags and frequency accordingly.
Change-Id: I8473072069da4532406ce720a0070a665e29b1af
Crs-Fixed: 3103939
