On reception of vendor specific action frames, host performs basic sanity
on vendor specific action frames fields and then forwards to supplicant.
Change-Id: Ib22b9a431411fff8128e461972b81b66688a0919
CRs-Fixed: 2897656
If firmware sends the TWT teardown due to concurrent session is
established, then the wait for notify flag is not set. So other
commands can be sent to firmware.
In case of TWT teardown due to concurrency, set the wait for
notify flag.
Change-Id: Ia1d5134e1c6d931f8c5ced1c011efb3489d343ad
CRs-Fixed: 2919799
Use wlan_reg_chan_has_dfs_attribute_for_freq API to check DFS
attribute flag instead of unused wlan_reg_chan_has_dfs_attribute
API as part of regulatory clean-up effort.
Change-Id: I7ff75f56ebd641d500c365f756526b787986dcbe
CRs-Fixed: 2908159
Currently Kbuild handles WLAN_CONFIG_OVERRIDE directives by writing
the overrides into a file and then including the file. This violates
one of the requirements of the Hermetic Build feature which forbids
modifying the source directory. This is also subject to a race
condition where multiple concurrent builds attempt to write to the
file in parallel, and one of the builds ends up consuming the
overrides from both builds.
To avoid these issues update the WLAN_CFG_OVERRIDE handling to no
longer use a file, but to instead just $(eval) the overrides.
Change-Id: Iac159228a82b0a8134e272ce63ed568050e8e6ae
CRs-Fixed: 2917351
Add support to reject the TWT setup request if there exists
another TWT session with different dialog id.
Change-Id: I59c0ba4279581bad14bec886d22c0ac65838ec17
CRs-Fixed: 2920494
Currently, mlme_twt_is_command_in_progress() function checks if the given
command is in progress or not. For inputs like WLAN_TWT_ANY, if this function
returns true then from the current logs, its not known which
active command in progress.
Hence for better debugging, enhance this function to return active command.
Change-Id: Ibc5c5babb042408b0e8988fe229d344ed98bfff3
CRs-Fixed: 2920494
As part of 11be enhancements, EHT operation and EHT capability
information elements were added. To support 11be in host driver,
define new APIs to handle these information elements in lim layer.
Change-Id: If615251cf874902263fe3c4faaf924fc9a3d9e23
CRs-Fixed: 2907952
As part of 11be enhancements, new information elements were added to
advertise the EHT capabilities in management frames. current driver
implementation supports generation and parsing of information
elements only till 11ax. Update the driver implementation to support
generation and parsing of information elements corresponding to EHT.
Change-Id: I3fd4067dc830b9fb5d603ae119fbb7ec6cfebe4e
CRs-Fixed: 2906976
The global aggregation size is only set to firmware once
when vdev is created. And the size may be modified
dynamically for a specified AP during association, according
to the OUI based aggregation size configured by ini
'cfg_tx_iot_aggr'.
If global AMSDU size is 0, considering the case as below:
1. connect to AP-1 which is included in 'cfg_tx_iot_aggr',
the AMSDU size will be set to the specifed value.
2. connect to AP-2 which is NOT in 'cfg_tx_iot_aggr',
it doesn't reset the AMSDU size to 0, and firmware is
still using the value set in step #1, it's wrong.
To fix this issue, set the global size for each vdev start,
as init values for each connection.
Change-Id: I790d580fc5762e6816e840ba5484b3cd758334df
CRs-Fixed: 2918046
KERNEL_SUPPORTS_NESTED_COMPOSITES := y is used to enable nested
composite support. The nested composite support is available in some
MSM kernels, and is available in all GKI kernels beginning with
5.10.20, but unfortunately is not available in any upstream kernel.
When the feature is present in an MSM kernel, the flag is explicitly
set in the kernel sources. When a GKI kernel is used, there isn't a
flag set in the sources. Therefore add logic to set the flag if we are
building with GKI kernel 5.10.20 or greater.
Change-Id: I13cd1a07915e9d187da22259cc61d9481e908e79
CRs-Fixed: 2914541
check if runtime pm enabled in wlan_hdd_runtime_resume
and wlan_hdd_runtime_suspend.
Change-Id: I107f953d19ea6078d8bb8a59d51dcac6736ff914
CRs-Fixed: 2920169
Update comments for temp change done to enable connection mgr, as
CONFIG_CM_ENABLE will be removed once Connection manager
LFR2 changes are done.
Change-Id: I22bc1f3f9fe5a69206ac496e99a60beb87dc1e36
CRs-Fixed: 2921657
As part of WiFi ini clean-up FR, the ini gReorderOffloadSupported,
is identified as an obsolete parameter. Hence it is deprecated and
all instances of the config CFG_DP_REORDER_OFFLOAD_SUPPORT is
replaced by default value of ini.
Change-Id: I738406fb740f414fb6ad70603dfc95b9bf137ac4
CRs-Fixed: 2916527
Extract the 11BE flags advertised by FW in WMI_SERVICE_READY_EXT2_EVENTID
and update the regulatory pdev wireless modes. The wireless mode is
currently represented as 'uint32_t' and all the 32 bits are exhausted.
To accommodate the new 11BE flags, change the data type of wireless_modes
from 'uint32_t' to 'uint64_t'.
Change-Id: I9c137fe4c3d6f28cf0b4e0dcb0ea5aae01b1749e
CRs-Fixed: 2906216
HSP doesn't support TX_AGGREGATION_SIZE ini, need disable it to avoid
confusing.
Change-Id: I9e49ad5218f913f116cf4472f768f572740f14df
CRs-Fixed: 2918796
Currently if STA is connected to HT only AP and if BW change
due to OBSS scan the htSupportedChannelWidthSet is not updated
and thus TDLS peer which use htSupportedChannelWidthSet to get
BW may not consider the vdev BW for HT and thus peer's BW can
go beyond VDEV's BW.
Fix this by updating htSupportedChannelWidthSet on vdev restart
on HT BW change
Change-Id: I7253fd240206ec27eac3e2b1de8debf8705a8234
CRs-Fixed: 2920539
In the current implementation of the function
__wlan_hdd_cfg80211_set_wifi_test_config, if the status returned by
get_cfg API is not Success, it returns from the function without
freeing the allocated memory. This causes a potential memory leak.
To avoid this, free the allocated memory properly.
Change-Id: I5f9ac5f2edc49ebad662f18dbe09893f8bee6459
CRs-Fixed: 2918850
Refactor the code to replace htt tx data header with packet capture
header. So that we can add extra parameters in packet capture
header to send required data to packet capture callback function.
Change-Id: I863c63b925d1cd8ba5a8a7f0bc08ee3cd2acb96b
CRs-Fixed: 2916795
As part of I418be56d452389a9f7b8d48e28f793567e81767a due to copy
paste error in cm_roam_scan_offload_fill_lfr3_config the pmk was
copied to rso_11i_info instead of rso_11r_info.
Fix this by copying pmk to rso_11r_info.
Change-Id: If4d1ea23ab4b4c43db3fac78fbfd43ad74a7e1b4
CRs-Fixed: 2920206
Currently the rate, ofdm and cck flags are filled to support only
legacy rates.To support other rates too, fill ofdm and cck flags
based on phymode and fill rate in terms of 500 Kbps in tx status.
Change-Id: I972919ebd2cbd19a1b55af0324e481fada7f12cd
CRs-Fixed: 2917079
1. If the TWT setup parameter re-negotiation results in failure,
then host driver shall trigger TWT teardown for the
existing TWT session.
2. Upon receiving the TWT teardown confirmation from the firmware,
host driver shall cleanup TWT session, send teardown notification
to the user space and ready for next TWT setup command.
Change-Id: I553ae7de8d900a3dc12d563b781f9fefa36f8a0b
CRs-Fixed: 2916548
The feature HIF_DETECTION_LATENCY_ENABLE is not applicable for all targets.
To avoid issues, enable this feature based on target.
Change-Id: Ia7bab02710ee2bbb9f487571ec98992ac338961f
CRs-Fixed: 2915968
Currently FW dbg log levels are configured for every vdev creation.
But this is pdev level configuration and doesn't required to configure
for every vdev. Because of this WMI commands are getting flooded.
To avoid this, configure FW debug log levels only for first vdev
creation.
Change-Id: Ie395c1a7b0756a08ad7948997531c6920d83ae0b
CRs-fixed: 2913901
In STA+SAP mode, disable pipes is not done as part of either
last client disconnection or SAP down. In the scenario where
APPS suspend does not get triggered, IPA pipes are not disabled
and on runtime suspend, PCIe link is suspended which would result
in a NOC error if IPA HW accesses wlan registers.
Fix is to avoid runtime suspend if there are any pending IPA
tx completions.
Change-Id: I190da658d233cb5d6c85846312ddc7a251f9f9d5
CRs-Fixed: 2918334
The userspace doesn't expect TWT teardown or notify events after
roaming. So to clear the driver internal TWT context, for old
peer, call the mlme_init_twt_context() on roam synch complete.
Change-Id: If1e4fe2d79561885052caf8d5231d1c943f10c96
CRs-Fixed: 2912872
