Log the AP link_id as part of the connect information log which helps
in debugging.
Change-Id: I5244e6c1d2cec905005515078839c0feda721a29
CRs-Fixed: 3508511
Upon the completion of roam sync indication event, the
roam sync complete cmd is first sent to the firmware.
This is followed by the netdev queues enable. This
approach adds latency in the first downstream tx frame,
and the FT roaming KPI is not met due to this latency.
To fix this, if roam sync handling is successful, enable
the queues and then send roam sync complete to the firmware.
It's observed that the current change improves roaming
latency by 6 msec.
Change-Id: Ib05ca01892b6d8b62badcafb64bb8c16270ee9f8
CRs-Fixed: 3483751
When disable puncture, no bandwidth indication ie exists in channel switch
wrapper, only wide bandwidth ie exists, need reset puncture to 0 when
handle csa event.
Change-Id: I6d311b52c984f354fbc359c6f5b5122b2a612b91
CRs-Fixed: 3512000
Initialize the link vdev with the default invalid vdev_id,
or else driver is returning wrong adapter for the query
resulting in invalid uninitialized access.
Change-Id: I4d2659d8ff1bfe42f14608e632bcc92ffb5d6963
CRs-Fixed: 3512102
In case of SAP, update the cfg80211_new_sta with the support for the
ML STA client with below info:
1) MLO link ID of the AP
2) Station's MLD address
3) (Re)Association Response IEs sent to the station
Change-Id: I5647d5bcfac43255bc0ae1d9f3b7a1b563ef5250
CRs-Fixed: 3485476
After ML STA link state changes, the connection table will
be updated. So defer the force SCC a few second to use
updated table to do force SCC.
Change-Id: I453b1a8d2707bb635f7c1d8d5b397811bf3b4f7b
CRs-Fixed: 3502411
If fcc constraint is set host disables all 6 GHz channels
except for the STA, P2P client connect 6 GHz channels,
but host shouldn't scan any 6 GHz channels.
Add changes to filter out 6 GHz channels from scan list.
Change-Id: Iffd64eb3a915158c77c781e6cb8813bc5204d840
CRs-Fixed: 3481012
To set fixed 11be rate, 11be_rate sysfs entry is the only
option. sdxpinn target supports Wifi-7 and hence 11be_rate
sysfs entry is needed.
Change is to enable WLAN_SYSFS feature on sdxpinn target and
at the same time disable CONFIG_WLAN_SYSFS_RANGE_EXT, which
is not needed.
Change-Id: Id468ee15b3ddc82794ab12487f21e06a0b61b209
CRs-Fixed: 3510104
Currently if AP+AP SCC on 5 GHz, next AP prefer on 2.4 GHz,
If SBS mode support, next AP can prefer also on SBS channels
and other MCC/SCC channels.
Change-Id: I3e44fd381527cae24aeff14f9158621f14a278b3
CRs-Fixed: 3499268
Currently roam pcl is updated after roam, connection and CSA.
Pdev current channel list is updated for many other scenarios,
but roam pcl is not modified accordingly.
To address this issue, update roam pcl every time after computing
pdev current channel list.
Change-Id: Ie86d5592255419de8f4040a3206d275ef926cf03
CRs-Fixed: 3481026
Currently host disables 6 GHz band when set_fcc_channel cmd
is received hence existing STA/P2P client 6 GHz connections
get disabled.
Add changes to keep existing STA/P2P client 6 GHz connections
intact and also keep SAP up on 6 GHz if STA+SAP SCC on 6 GHz
channel was present before receiving this command. Disable all
other 6 GHz operations.
Change-Id: I95c094e1b344d430a288b6f613842efe6e576e25
CRs-Fixed: 3495006
Currently the CDP handles like soc/hif/hal_soc are not
available in any of the the DP component contexts.
Modules like FISA etc need these handles.
Store the CDP handles like soc/hif_handle/hal_soc in
the DP component context.
Change-Id: Iaee4d0e15cbaa7d871dc9e246d177ad310b4c6ba
CRs-Fixed: 3505720
Currently host doesn't check if 6 GHz band bitmask is set
when receives SAP start on a 6 GHz channel. This can cause
SAP start on a 6 GHz channel when set_fcc_channel is set.
To avoid this issue, reject SAP start on a 6 GHz channel
if 6 GHz band bitmask is not set.
Change-Id: I0dd2b1fac7c4293498f7747665302bd72b7aaa23
CRs-Fixed: 3481002
When SAP is on 5 GHz or 6 GHz channel other than the user
configured frequency due to concurrency and concurrent STA has
disconnected, then SAP doesn't move back to the user configured
frequency when MCC to SCC Switch mode is 4
(QDF_MCC_TO_SCC_SWITCH_WITH_FAVORITE_CHANNEL). SAP has to move
to the user configured frequency irrespective of the current
operating band.
Move the SAP to user configured frequency when SAP is standalone
after STA disconnection.
Change-Id: I3fb78cbd949c0e2ec7c393208569956dbcdd067a
CRs-Fixed: 3509288
Chan width 1 in vht operation means >=80M, while chan width 1 in eht op or
he op means 40M, need be handled in different way.
Change-Id: Ib65dca6245c33f07df351b6ac7eed86f91b372c7
CRs-Fixed: 3506080
Move below two fields from hdd_stats struct to hdd_adapter
1) is_ll_stats_req_pending
Stats will be requested on adapter and in case of MLO
the bitmap of VDEV is send to FW to request all associated
VDEV's stats.
2) sta_stats_cached_timestamp
As stats for each VDEV in adapter will be queried in one
request to FW, the timestamp of last stats update is per
adapter.
Change-Id: I7291e7700a4e6de47196869731b4fdf353a17e78
CRs-Fixed: 3451925
To get the associated state of each underlying vdev in
adapter, this API needs to be called with link info
argument to get the corresponding vdev.
Modify the function prototype to take link info as
argument instead of adapter.
Change-Id: If7d0d3930581df644905ffccaa355a2e32de46e0
CRs-Fixed: 3451564
Add ECSA Target TSF attribute in QCN IE. This attribute
will be included in regular ECSA public action frame and
will be use to send target_tsf and twt_switch_mode to
earbud during LL_LT_SAP CSA.
Change-Id: Ic86bf1b4e8e8516a5774371815d7566f00fee12a
CRs-Fixed: 3490521
Build failure is seen with CONFIG_SYSFS=y and
CONFIG_FEATURE_BECN_STATS=n.
Fix is to add stub declarations for
hdd_sysfs_create_bcn_reception_interface and
hdd_sysfs_destroy_bcn_reception_interface.
Change-Id: I1b1522305ea40d524e9a354211a2e38d4b4cb9d5
CRs-Fixed: 3508273
To get the adapter, wlan_hdd_get_adapter_from_vdev() calls
hdd_get_link_info_by_vdev() which will return link info.
As vdev is moved to per link data structure, modify the API
prototype to return link info pointer and rename as
wlan_hdd_get_link_info_from_vdev().
Callers can get adapter in the link info structure.
Change-Id: I579796ab395515bb777f3204528287b4595c60a7
CRs-Fixed: 3451442
Currently the txrx_ops are not saved in the
non-converged datapath.
Store all the txrx_ops in DP component, when
they are registered with the vdev. This can be
used in the DP component to get and use these
ops.
Change-Id: I30bfc69a32e0a9f0ab16f902a94a8c28ef4af8a6
CRs-Fixed: 3505719
In the hdd_get_adapter_by_vdev() check all the links to find
the adapter that matches the input vdev_id.
Change the function prototype to return pointer of link info
instead of adapter and rename API as hdd_get_link_info_by_vdev().
Callers can get adapter in the link info structure.
Change-Id: Iec5b5b476f74a35054802510093f81e158be2d65
CRs-Fixed: 3451007
Enable changes to affine away CPUs taken during pro
audio use case for kiwi_v2.
Change-Id: Ie27009ae0c89b5a08887863658ccc8cfae47c324
CRs-Fixed: 3490850
The logic to allow peer create on same ML dev context is useful to allow
connection to ML-AP with same link address and MLD address, but it will
allow duplicate peer for ML-SAP.
If a legacy client is already connected to ML-SAP and new ML client
initiates connection with MLD address same as legacy client MAC address,
the rejection logic during peer create fails as both legacy and new ML
client belong to same ML dev context.
During peer create if a duplicate entry found in ML dev context, only
allow if the duplicate entry is on different VDEV, if it is on same VDEV
reject the peer create.
Change-Id: Ic82f80d814e21ea0b69ffd960e7aaef4ebc80ebf
CRs-Fixed: 3496058
On reception of reassoc req from user space to the
connected AP, wlan driver proceeds with reassociation
without clearing the keys. This leads to encrypted EAPOL
frames in LFR2. To avoid this, trigger disconnect & delete
keys before proceeding with reassociation.
Change-Id: Ib287b5d43ae69a7696a28f0e59347c7376d581c3
CRs-Fixed: 3505422
Currently, eMLSR concurrency API considers both the links to
decide whether to allow or disallow the command while
force-enabling links. But one link might have got disabled to
handle some concurrency and might not be present in the
policy mgr table. Driver has to consider the links that are
present in policy mgr to allow/disallow link-enable command
when an eMLSR connection is present along with other concurrency.
Also, user might try to force-enable the disabled link. Allow
that only if eMLSR concurrency is not present.
Change-Id: I0a68059b7d16629016b3c40dbc0345523d46ef21
CRs-Fixed: 3500106
Currently as part of LL_LT_SAP optimization, driver receives
do_acs command from below two path
1. LL_LT_SAP library to get the channel early and
2. Hostapd during SAP turn on
In the first request if driver finds the clean channel as part
of partial scan req then it directly sends that channel to
requested module. So in the second request, driver will exclude
the recently scanned channel from scan list. But there may be
possible that it may receive another clean channel during scan
which leads to two different back to back ACS frequency.
To avoid this, store the current acs frequency and if driver
receives the second acs req within 500ms then send the stored
acs result to requested module.
Change-Id: I9b083a64e996f6ada32ff5210a304aa66aa6ec3a
CRs-Fixed: 3498271
