Currently driver process SET_TX_ANT_CONFIG command for
asymmetric tx/rx nss values, but it's not correct to
have asymmetric tx/rx nss values before connection
as connection will always happen in 1x1 or 2x2.
To address this issue, reject SET_TX_ANT_CONFIG cmd
if TX nss and RX nss values are different.
Change-Id: Id6f3ff57ae3a991192b76bd476034867a799d95e
CRs-Fixed: 3485059
Currently, Fw did not set NACK reason code
to Host when Fw is not ready for WoW.
As part of the new change, Fw will send NACK
reason code along with WoW NACK to host.
Make changes in host to store and print
NACK reason code.
Change-Id: Ic978af9572c8de37df3fb926083aac5e6ddefda7
CRs-Fixed: 3481177
As part of single netdev multi vdev changes, AP context is
now per link. To get the SAP context pointer from AP context,
pass link_info pointer instead of adapter.
The existing callers are moved to deflink pointer.
Change-Id: If49ce9dcbf58710d8184dfbef1d0a99567f3111b
CRs-Fixed: 3448342
When user space use "iw dev" to get tx power info,
driver send WMI_REQUEST_STATS_CMDID to fw,
fw update tx power info with two events, usually we
parse the last event, and maybe get invalid value.
Filter invalid value for each event, and get valid
tx power value from the mac which the AP/STA mode work.
Change-Id: I2411bb87e03fe385759852b028819e19a055b7f3
CRs-Fixed: 3474361
Enable the tracepoints for qca6390 module in the wlan host for latency
debugging.
Change-Id: I9f69a5d9cc08a63185961bf2a88d403bb62799e8
CRs-Fixed: 3497709
There is a typo for the feature flag ENABLE_HAL_SOC_STATS. Thus,
correct it to -DENABLE_HAL_SOC_STATS.
Change-Id: Idc7e478480e799659c971e42962e9d527960a9da
CRs-Fixed: 3492601
While handling CSA Wide BW IE to switch freq, driver update the
PE session bandwidth and limit the switch to existing bandwidth.
This result in failure while checking if new bandwidth is same
as previous bandwidth and thus bandwidth change fails in this
case.
To fix do not update PE session while handling CSA Wide BW IE and
do not limit the switch to 80 MHz. Also add current Bandwidth
info in logs.
Change-Id: Icb1f169b17f711df91fd10230d6fdfd9a3d30274
CRs-Fixed: 3498943
Host driver sends deauth to AP BSS if the ML Info
IE is not present in the auth frame, but doesn't
abort the connection. Later, upon auth failure timeout
the connection gets terminated.
Instead of waiting till timeout, abort the connection
if the authentication fails.
Change-Id: I61e429baf29c49e4b28f379a9f4870dac7de5217
CRs-Fixed: 3497640
The UL MU MIMO capability is neither supported by SAP nor
STA. In the case of ML STA, reset UL MU MIMO capability on
all its vdevs.
Change-Id: I14ba48aceade0ac4fd85aa66a6dda54748c89a03
CRs-Fixed: 3487893
1. When handle STA CSA, find only puncture bitmap changed, primary freq and
bandwidth not changed, still continue CSA.
2. When Updated beacon has no eht op info, need look up he/vht op to get
channel info.
Change-Id: Ib5270a1245e0dd9ba095c63f2bea959dd9ddac44
CRs-Fixed: 3499067
Fix the EHT MCS rates for 5 GHz 20 MHz-only testbed STA.
This allows for the required MCS rates 0-7 and 8-9 to be
enabled that were currently reset in set EHT testbed
defaults API.
Change-Id: I13555882c68e5b5454415d5a63cc02d12be5f43a
CRs-Fixed: 3487863
Toggle the MSB of last byte while deriving the link MAC address to
increase the MAC address range and avoid deriving duplicate MAC
addresses.
Change-Id: I2ba1d8bcfaa95fd5291202316106d9b0dd74766b
CRs-Fixed: 3499105
When STA roams from multi link AP to single link AP, because MLO link
vdev is not disconnected yet, PCL is updated according to MLO station
connection and SLO station connection concurrency scenario.
After MLO link vdev is disconnected, PCL should be updated again
according to SLO station connection scenario.
Change-Id: I6a297c05a605fefe27c20a90d36e419819e6415d
CRs-Fixed: 3497055
Currently, packet capture packets are processed until the mon list
is empty. There can be situation that while mon list is not empty and
mon thread is running, mon interface is deleted and as part of it
PKT_CAPTURE_REGISTER_EVENT is cleared. After clearing the bit, interface
deletion will wait for completion of mon_register_event and flush the
remaining packets in mon list without processing them. In this case
as mon thread is already running and processing the packets from mon list
without check for PKT_CAPTURE_REGISTER_EVENT bit, it may lead to
timeout in deletion of mon interface in case of high throughput scenarios.
To avoid this situation, add a check to test PKT_CAPTURE_REGISTER_EVENT
each time before processing a packet from mon list.
Change-Id: I21e7adc0149c2330f6008d54db8576ca705f2b55
CRs-Fixed: 3475349
Tx power not set in case when user sets tx power as auto.
When user set tx power as auto now, host will configure
the tx power as max regulatory power allowed for
that channel. It signifies that it is the upper
limit for tx power used while transmission.
Change-Id: I98e53e417fa72c58ef8b22017a9a622ba8ccb257
CRs-Fixed: 3478243
1. While populating t2lm ie use dynamic memory allocation
instead of static and free after usage.
2. If AP rejects T2LM action req frame, sends status code
anything other than 0(success) or 134(preferred mapping),
clear ongoing negotiation.
Change-Id: I50fbf34f3e95bbeaf13c2e1a74374b22837dffa8
CRs-Fixed: 3496677
Currently, host driver disables eMLSR STA link when a SAP is
coming UP. Once the SAP is UP, host driver evaluates the current
concurrencies and re-enables the link if it can. This allows the
driver to bring UP disabled link(if any) as the SAP would do SCC
with one of the ML-STA links. But this is not applicable for
eMLSR STA. No other concurrency can co-exist with eMLSR STA
currently. So, one link has to be force-disabled always to let
the firmware not enter into eMLSR mode.
So, don't allow the validation of current concurrencies in
policy_mgr_handle_sap_cli_go_ml_sta_up_csa() eMLSR API
policy_mgr_handle_emlsr_sta_concurrency() takes care of
eMLSR concurrencies.
Change-Id: I78a15447a8ea5a3a98146d9c9b577095bb8496de
CRs-Fixed: 3492030
Currently the 11be capability is set to true from host if the
11be macro is enabled intersect the same with the ini configuration
and update the feature set accordingly.
Change-Id: Ifbd4207a5113fafe5e8ebb87c6b7fce6c2a29eff
CRs-Fixed: 3495617
Currently, as part of wlan_hdd_stop_modules, direct link config
is not being cleared but hif link state vote is cleared, as a
result when hdd_close_adpater() is called, link state is already
cleared, resulting in crash, as config is still enabled.
To fix this, clearing config as part of direct link context
de-initialization.
Change-Id: I1a5de6f427b5bc4dc4fe4346e53354645ad53529
CRs-Fixed: 3495027
Currently, on receiving scan events from FW, the host is
unable to populate the channel info buffer.
Populate 6 GHz channel info in hdd context from wiphy
as per NL80211_BAND_6GHZ band.
Change-Id: I726a43d0f2bbf6c8dfc405cfa917f8dfc8a8e0cd
CRs-Fixed: 3488036
Vendor command pre_doit holds wiphy lock inside kernel and calls
into driver vendor command handler and from driver vendor command handler
if unregister_netdevice() is called it will try to acquire same wiphy lock
inside kernel cfg80211_netdev_notifier_call() and deadlock.
To fix this issue from driver vendor command handler for pre CAC adapter
stop call cfg80211_unregister_netdevice to avoid recursive wiphy locking.
Change-Id: Id939016c1baf730707346f2375d0b952017a48f5
CRs-Fixed: 3493940
STA is on 5 GHz 5260, SAP on 6 GHz 6415, GO on 5 GHz 5745.
STA receives CSA event to move to 5540. Then 3 vdevs are
MCC in 5 GHz high band which is not supported by target.
And we should avoid SAP+GO on same band MCC.
Fix by:
1. Check allow concurrency for STA CSA for more than 2 connection
case.
2. change SAP PCL to only includes SCC 5 GHz channel and 2.4
GHz channel to avoid SAP choosing 5 GHz MCC channel if STA+GO is in
SBS mode.
Change-Id: Iadf8cfd215393baf4823c0e7cb6aa3656d8004dd
CRs-Fixed: 3482252
The four SAP concurrency pcl table is deleted by change:
I494e7a8d6ecc0a550027ff7f64de5deb11b987a9, it is still needed
for MDM platform, otherwise the 4th SAP will be rejected by
policy manager.
Add back original four SAP concurrency pcl rules.
Change-Id: Ib80c58f114f494a2c66fc15286b1a434d577dd26
CRs-Fixed: 3490580
As part of single netdev multi vdev changes, AP context is
now per link. To get the hostapd context pointer from AP context,
pass link_info pointer instead of adapter.
The existing callers are moved to deflink pointer.
Change-Id: I01ef675de40779b386b72a033e76806488bc36e7
CRs-Fixed: 3447737
As part of single netdev multi vdev changes, AP context
is now per link. To get the AP context for a particular
link, pass the link_info pointer instead of adapter.
Change-Id: I0ffbafdf5c73c47d8ba335706d4065d55b7e45cb
CRs-Fixed: 3447599
The existing code do not check CONNECT_REQ_MLO_SUPPORT flag and
driver connects in MLO with ML capable APs. This leads to auth
timeout incase of SAE as the MAC address in auth frames are
different.
Userspace connect request params will enable CONNECT_REQ_MLO_SUPPORT
flag to indicate driver can connect to ML candidate for that connect
request, incase this flag is not set in the connect request the driver
shall downgrade to non-ML connection.
Change-Id: I1452c0b61d86d23103ccd84c142e99f79d2077f7
CRs-Fixed: 3477110
Scan module already print the info of the beacon/probe response
Remove the repetitive logs from LIM which are not useful.
Change-Id: I609f229a7242c5d58081d44f2d9c1447e089c648
CRs-Fixed: 3490645
Currently when driver receives SET_TX_ANT_CONFIG command, it
doesn't check if tx/rx nss values are allowed for the
existing connection and sends chain mask configuration
command to fw.
To address this issue, reject SET_TX_ANT_CONFIG command,
if given tx/rx nss value is greater than connection's
intersected nss.
Change-Id: I58078d8dd6c9e04ccedad26b79a7dc3a040e9ef6
CRs-Fixed: 3476639
When the Intra band INI is enabled and the STA connected in 6 GHz
band the channel count and frequency are not sent in the
WMI_ROAM_CHAN_LIST command as the band is not defined or unknown.
As a result of this DUT is unable to trigger partial roam scan in
the current connected 6 GHz channel and does a full roam scan.
Add the 6 GHz band check in the Intra band enabled case.
Change-Id: I765c233d1e6bf71cab186041ebd7df2293be6f05
CRs-Fixed: 3469197
Currently as IPA_OFFLOAD path is enabled for OPT_WIFI_DP
usecase, this causes SAP/GO D3 WOW to be disabled.
This change will add a check to ensure D3 WOW is
enabled when IPA path is set for OPT_WIFI_DP usecase.
Change-Id: Ibec94ca172646c80fa9ec7e6ff24e6e5f6fcad60
CRs-Fixed: 3472752
