Currently, Stats request commands are sent over qmi right from the
target suspend request is sent to FW. This is leading to a crash in
FW since it is trying to access PCI when it is in suspend state.
To address this, send stats request over QMI only after the ack is
received for the target suspend command.
Change-Id: I1b2b6a60c5d8c7ec4375d328e58a66d749794e3f
CRs-Fixed: 2835903
Replace generic WLAN_OSIF_ID by functionality specific dbg id
with API hdd_objmgr_get_vdev_by_user.
Change-Id: I06e1e14a998377e36ae533eec914eb3b61b6c165
CRs-Fixed: 2839542
This change, separates out connection manager code and
non-connection manager code for disconnect flow, based on
the feature flag so that only required part of the code
is compiled.
CRs-Fixed: 2838853
Change-Id: I853cc587a013a23359f5109c6c32a50597cb6232
This change, separates out connection manager code and
non-connection manager code for connect flow based on
the feature flag so that only required part of the code
is compiled.
Change-Id: Id0b22f03939b044eb66e6cd2787b356e50710262
CRs-Fixed: 2838864
If firmware supports NAN discovery vdev then one vdev is
reserved for NAN. Do not reserve NAN discovery vdev in case
of FTM mode.
Change-Id: Ie16df46bbb09dd89889639d40dc1a65e3786ce73
CRs-Fixed: 2830136
Add ini to set init chain mode for BTC, default value should
be set to the same as macro WLAN_COEX_BTC_CHAIN_MODE_UNSETTLED
that means no need to send init chain mode for BTC to firmware
in wma_vdev_pre_start() process.
Change-Id: I3051a7f8a0c708c7df40d1b95b46e0bfa6892f6c
CRs-Fixed: 2837173
MCC does not use DFS_BANGRADAR feature so move common code
related to DFS_BANGRADAR to WIN specific code and as part of
this remove dfs_full_offload.c file from MCC compilation.
CRs-Fixed: 2837274
Change-Id: Ie28568a317787a0fb43dd94058f7b3e425bc3929
While pre cac is in progress and if the SAP is stopped from UI, It may
lead to dead-lock due to rtnl lock. This is because, stopping SAP will
trigger the stop_ap first and then hostapd_stop. Stop_ap will schedule
a work to handle pre_cac failure (Thread1). hostapd_stop will be
triggered in parallel (Thread2). This will result in a below dead-lock
scenario.
Thread1: Waiting to acquire rtnl_lock to unregister pre_cac adapter.
Thread2: Acquired the rtnl_lock and waiting for Thread1 to complete
To resolve this dead-lock, unregister pre_cac_adapter during
hostapd_stop without requesting for rtnl_lock.
Change-Id: I222df9ee0d75b16f79c28b7cdd86369c340a15c2
CRs-Fixed: 2832256
DUT can't connect some WAPI AP by ASCII due to
lim_process_assoc_rsp_frame: received Re/AssocRsp frame failure code:
40.
Current Some WAPI AP cannot accept Vendor Element ID: 221 length > 11,
and reply reject ASSOC resp by reason code 40.
Because we extend Vendor Specific element to include MCS12/13 from HSP.
So only HSP meet this IOT issue.
Qualcomm Inc. - Specific
Element ID: 221 Vendor Specific [71]
Length: 15 [72]
OUI: 8C-FD-F0 [73-75]
Value: (12 bytes) [76-87] 01 01 02 01 00 02 01
01 09 02 03 00
Change-Id: If766ef280b685100ff4a409309d56ead717f251b
CRs-Fixed: 2836011
For no scan case, FW sends 3 more tlv to host along
with 11kv info. This info helps user in debugging/
understanding the scenario when roam failure happens.
Print the info received related to btm,scan type,
trigger_id into into kmsg for no scan case.
Change-Id: I699a22cf344e6a554349bd5338471951d3dd3b4a
CRs-Fixed: 2835759
Modify IEs for 6 GHz processing.
Country IE - Make the first triplet mandatory and keep
rest of the triplets as optional as 6ghz channels are
denoted by operating class/subband sequence and the
triplet field will have details about it.
transmit_power_env IE - Rename vht_transmit_power_env to
transmit_power_env and add 3 new subfields-
Max tx_pwr_count - indicates the number of local max tx
power For X MHz fields (where X = 20, 40, 80, or 160/80+80)
minus 1 in max tx pwr field of the TPE element.
Max tx_pwr_interpret - indicates the contents of max tx power
field (local EIRP, Local EIRP PSD etc) and interpretation of
the max tx power count field.
Max tx_pwr_category - indicates a category for which max
tx powers apply. A value of 0 indicates the default category;
the interpretation of other values depends on the country.
HE Ops IE - Addition of a 3-bit subfield Regulatory info,
reg_info indicates TYPE of the 6GHZ AP that is carrying this
IE in the beacon: this would typically be SP, LPI or VLP.
Change-Id: If6fbb8a92a6f80b6bcf18906494d08ff048d68a4
CRs-Fixed: 2822657
There are cases where only a few TWT roles may be required
to be enabled. For example TWT Requestor role alone or
TWT Respondor role alone. Also, it could be unicast TWT only
and disable broadcast TWT.
Support broadcast TWT configuration in requestor and responder
role by adding new INI.
Extend the use of existing requestor and responder INIs to further
enable requestor and responder roles itself.
Change-Id: I3dfa196edfda9cafd01fa56c0bb6ce73e27b4144
CRs-Fixed: 2828718
Increase the number of TWT peers allowed to 32 from current
default value of 2.
Change-Id: I9c081f602af059c940223ea2f66ea257a7d44f07
CRs-Fixed: 2825861
In the customer platform, the chain0 for 2.4G is disabled,
it just only support 1x1 2.4G + 2x2 5G for hasting. With
such kind of configuration, 2.4G SAP start failure due to
policy_mgr_is_hw_dbs_required_for_band return false with
following config, which block switching hw mode from single
mac(single mac just only support 5G) to dual mac and then
make start 2.4G SAP failure on single mac configuration
[0]-MAC0: tx_ss:2 rx_ss:2 bw_idx:5 band_cap:2
[0]-MAC1: tx_ss:0 rx_ss:0 bw_idx:0
[0] DBS:0 SBS:0 hw_mode_id:0
[1]-MAC0: tx_ss:2 rx_ss:2 bw_idx:5 band_cap:2
[1]-MAC1: tx_ss:1 rx_ss:1 bw_idx:4
[1] DBS:1 SBS:0 hw_mode_id:1
Change-Id: If9e76fb47743c32c313eacf150146ba8fa60eb2d
CRs-Fixed: 2833620
Currently connect/disconnect flow is not enabled for connection
manager, enable connect/disconnect path for the connection
manager.
Change-Id: Ibe83639fb7191169aa6be819edbc94ff086c9f5d
CRs-Fixed: 2830693
Currently driver does not consider kernel version
when it updates max he mcs index, kernel version
prior to 5.4 supports max he index as 11 and while
5.4 kernel version onwards max he index 14 is
supported. In current implementation driver might
update max he index more than 11 for kernel version
less than 5.4 also which is an invalid value for kernel
version less than 5.4.
To address above issue update correct max he mcs index based
on kernel version.
Change-Id: Ic011f647dcdfa6c039a3f1299364ac337820a656
CRs-Fixed: 2826282
It doesn't handle failed case about getting vdev or tdls vdev object
when teardown tdls connection. Which causes reference count of psoc
leak.
Change-Id: Ie4e7966c0a07f378483cd5e6344599645c75ac68
CRs-Fixed: 2836949
Target added a new thermal level - THERMAL_SHUTDOWN_TARGET
to indicate that target will shutdown entirely.
Report QCA_WLAN_VENDOR_THERMAL_LEVEL_EMERGENCY to upper layer
for equal or above of THERMAL_SHUTDOWN_TARGET.
Change-Id: Ic617411cda326b954511d2d41a595685b379447b
CRs-Fixed: 2835959
Currently, STA reconnect (e.g. reconnect to same BSSID) is handled
as STA+STA as part of NAN concurrency checks. This results in NAN
disable when reconnect is issued.
Check if the current incoming connection is on same vdev as
previous sta connection instance and disable NAN only if it's
different.
Handle NAN+SAP reenable in similar way.
Also, remove the redundant usage of NDI cleanup API
ucfg_nan_check_and_disable_unsupported_ndi in
if_mgr_connect_start.
Change-Id: Ia063a69bb2efdf1d51c6988b8905ceac0f454dab
CRs-Fixed: 2821352
To avoid roaming enable failed for operations bitmap set/clear mismatch for
SAP+STA or STA+STA concurrency, clear whole operations bitmap when RSO
deinit, then roaming can be enabled again after STA disconnect and
reconnect.
Add log when set/get operations bitmap to help debug.
Change-Id: Ie1f1a213dcdefb393ec3e1e2c6a8a71ab17b226c
CRs-Fixed: 2834199
As a part of SAP CSA, host deletes all peers if the new channel needs
CAC. Host deletes all peers from lim and doesn't give STAs delete
indication to hostapd. Hence after deleting all peers from LIM, update
stations delete indication to hostapd.
Change-Id: I833cf7b39b78c20f9a972a47461401baa485d101
CRs-Fixed: 2825720
During dp_rx_fst_cmem_deinit, free dp_fisa_rx_fst_update_elem
from the fst_update_list.
Change-Id: Ie3445bc4b06cba3e72cf44fe09417b9528115c1e
CRs-Fixed: 2833805
