Currently, host exits the regulatory update critical section as soon
as hdd_regulatory_dyn_cbk finishes. However, there is some work that
is scheduled to send the updated scan channel list to FW, which needs
to go inside the critical section as well. Move the logic to exit the
critical section after host sends the channel list.
Change-Id: I01f82232bdd4d4b3403f46dee5278fc74d50b05a
CRs-fixed: 2905643
As part of WiFi ini clean-up FR, the ini parameter
etsi13_srd_chan_in_master_mode, is identified as an obsolete. Hence,
it can be deprecated and use its default value for the config
CFG_ETSI_SRD_CHAN_IN_MASTER_MODE.
Change-Id: Ic695e36e9b4fc9952cc405d1345b4a6a7d543dad
CRs-Fixed: 2896031
When the SRNG IRQs are disabled during suspend, it is
required to disable the interrupts and wait for interrupts
that are pending to complete. Adding a pld/pfrm API to disable
irq synchronously.
CRs-Fixed: 2908685
Change-Id: Ia1f17d54cbe08e8dc101c0ecc2ddee9275712659
Set system state in hif ctx to suspend or resume on
system suspend and resume respectively.
Change-Id: If1904a4fe5c861deed1b35071be10cb8cc8d6407
CRs-Fixed: 2899520
Enable LPSS flag on SDX65 platform to make suspend/resume possible to
work in some special scenario like STA/SAP interface idle exist.
Change-Id: I703401d27d3437d0006ad560c00154b0dc589091
CRs-Fixed: 2873228
For sap mode, beacon frame has country IE, but country info
fields have all bands channels information. Using band based
chanel list to populate country IE information.
Change-Id: I0be084b9b539d453e5386c6a25dd2d9daa5de21c
CRs-Fixed: 2819683
Fix to pass assoc_info instead of address of assoc_info
to sme_qos_csr_event_ind() and cm_remove_cmd()
Change-Id: I9f6c12870954c42f2b1e6250e7547c45a593cae8
CRs-Fixed: 2911027
BSS max idle testbed test requires to prevent the data and
manamenet response frame Tx with user configuration.
Add support to prevent data Tx and drop Rx mgmt frames so that
response frames is not sent.
Change-Id: I01f08fd8f30dc4b1b80801434918b976abb09e3c
CRs-Fixed: 2817703
Any operation on the reject ap list should be protected
by the mutex lock, otherwise, race condition may happen
and result in list corruption.
Change-Id: Iefe0594a62563d800e85f8f6ebd747ab46c19fcf
CRs-Fixed: 2901576
As part of WiFi ini clean-up FR, the ini parameter ImplicitQosIsEnabled,
is identified as an obselete parameter and hence it can be deprecated.
Change-Id: Id2ea893ec714150d6144aead2dc3c2b5967d805b
CRs-Fixed: 2896059
As part of WiFi ini clean-up FR, the ini parameter gEnableLPRx,
is identified as it is no longer used. Hence it can be deprecated,
and all instances of the config CFG_LPRx is removed.
Change-Id: I77f8f6839534c9a79cb3c7414582a5f31b87c561
CRs-Fixed: 2896027
The current multi-ko support is achieved by creating, during the
actual build process, target-specific .<chip> symbolic links beneath
the qcacld-3.0 folder. Unfortunately this mechanism violates the
requirements of the Hermetic Build feature which requires that the
source directory not be modified during the build process.
To satisfy this requirement remove the dynamic creation of symbolic
links from Android.mk, and instead staticially instantiate all of the
required symbolic links in the git project.
Change-Id: I7d75bb6a82fd27d8925d53529b4252b782457bc8
CRs-Fixed: 2896976
In Kernel 5.4/4.19, CNSS2 will check if the current enumerated
device id matches with the device id in pld_pcie_id_table[]
by calling cnss_wlan_register_driver(). When using ROME, the
enumerated id is 0x3e, but it is not defined in pld_pcie_id_table
if CONFIG_AR6320_SUPPORT is not set. To avoid this issue, add
compilation flag for CONFIG_AR6320_SUPPORT, then set it in your
qcacld build env for ROME chip.
Change-Id: I7b0fee679923402c43487299e31696d847552335
CRs-Fixed: 2906988
As part of WiFi ini clean-up FR, the ini parameter
gDataInactivityTimeout, is identified as it is no longer used
and hence it can be deprecated.
Change-Id: Ic01ba8934058cf2fb3bec042f11b01ea70ef7a3f
CRs-Fixed: 2896042
wlan_hdd_state_ctrl_param_create() creates a control file that is
used to synchronize the wlan driver with the Wi-Fi HAL in
userspace.
Currently the driver creates the file at the path /dev/<module>.
The WIFI_DRIVER_STATE_CTRL_PARAM configuration item defines the path
that the Wi-Fi HAL uses, and this is /dev/wlan.
So when the driver is built with a module name of "wlan" the file is
created at the expected path. However when the driver is built with a
different name, as is done when TARGET_MULTI_WLAN is enabled, the file
is not created at the expected path.
Therefore change the driver to always create the file at the path
specified in the WIFI_DRIVER_STATE_CTRL_PARAM configuration item.
In addition do not even enable the functionality if the
WIFI_DRIVER_STATE_CTRL_PARAM configuration item is not set
(i.e. on non-Android platforms).
Change-Id: I8a7f0a9b22e3f49d02f896150bd452f80af9c022
CRs-Fixed: 2905381
Some SAP channel switch requestor will wait for channel switch
completion. Set sap qdf_event after sap hdd callback recevies
eSAP_CHANNEL_CHANGE_RESP.
Change-Id: I15e0733ac2bef6af55e02ff18f94cc2c86eb9811
CRs-Fixed: 2905918
Add change to support roam ho fail and roam invoke fail
indication in connection manager.
Change-Id: I8e4fed2ca4b9c6e95da86b0c37e39da8f2bc4953
CRs-Fixed: 2906319
TDLS teardown happens in high throughput
scenario as rx pkt count increment API
"tdls_update_rx_pkt_cnt" is not called
if hdd_is_current_high_throughput API
returns TRUE. The reason for this is due
to high cpu cycles consumed by
tdls_update_rx_pkt_cnt API.
As part of fix optimize tdls_update_rx_pkt_cnt,
tdls_update_tx_pkt_cnt API's for high
throughput scenario. In high throughput
scenario mostly the use-case is to increment
the pkt counter so move that logic to
the top of the API's.
Change-Id: I4eb0da3571c45b5ee91e051e251158af15f73973
CRs-Fixed: 2888746
When TDLS connection is made in 160 MHZ
for 11ax staions, the MCS rates for the
same aren't updated correctly.
Also, MCS rate can change in case the
connection between both stations is made
with AP operating in NSS 1x1, as there is
a check in lim_populate_he_mcs_set which
will disable MCS rates corresponding to
nss > 1x1.
To fix this, copy 160 MHZ mcs from the
staion parameters which gets updated in
change station. Also, use nss parameter
which is passed by lim_populate_he_mcs_set()
in the check which was used to disable mcs
rates corresponding to nss > 1x1. Thus,
peer station nss will be used to
determine whether to disable or not.
Change-Id: I23079aed3795202e6ae32583a220c1ed3227c1dd
CRs-Fixed: 2904540
Currently,there is an issue in hdd_adapter_iterator(), as it
is iterate till (n-1)th adapter. Due to this, in STA+STA+P2P
scenario, driver allows wlan0 scan when P2P connection in
progress as hdd_is_connection_in_progress() only check for
STA mode and miss the P2P mode.
Iterate till nth adapter as a fix.
Change-Id: Ia6e49b3a8372634756e89032ee9d599583160479
CRs-Fixed: 2907307
In Extended capabilities sent in assoc request, TWT capabilities
are included so 10 octets are present, but in set ie command,
only 9 octets are included.
Also the Beamformee STS <= 80Mhz capability is not populated
per band based on firmware advertised capability in the
set per band ie command, so there is mismatch in this field in
initial association and roaming.
Populate the missing bytes in IE sent via set ie command to
firmware, also update the beamformee sts capability per band.
Change-Id: I2d191cedface935970ed4f974c09c3b4c5acd477
CRs-Fixed: 2891017
Although sdxlemur attach HSP, but LFR3.0 is disabled and LFR2.0 enabled
in target, so add exception in default configure file.
Change-Id: Idabbe317fc0fcc194138beb7444d812cd60455a8
CRs-Fixed: 2854249
