Record station connect/disconnect event for debug connectivity
issues. Dump the latest 20 records for unexpected disconnect case.
Change-Id: Ibf04b98a0124b84b77e3b5647e4d4234189b0ab2
CRs-Fixed: 2849471
Update the validation for SA Query Request/Response to fix the
issue that these frames are dropped unexpectedly when OCI IE
is not present.
Change-Id: I57acd699fd5c7eba23551133e3439fe23c1949a4
CRs-Fixed: 2846717
Subscribe for offload Tx data wdi event and process offload Tx
data packets and post into mon thread for packet capture mode
Change-Id: Ic61043b8461eed4be5e8dc8d41baca2574224a90
CRs-Fixed: 2845598
HW assist is a FW feature and it is enabled by default. But there is
no provision to disable/enable this feature based on requirement.
To address this, add INI param to enable/disable HW assist feature
in FW.
Change-Id: Icdc4a842be4d5c6991a785ee270f61ba87fcfe79
CRs-Fixed: 2841346
In AP side power off/on case, AP security has been cleanup.
The STA side might still cache PMK ID in driver and it will always
use PMK cache to connect to AP and get continuously connect failure
in SAE security. This function is to detect AP off based on FW
reported BMISS event. Meanwhile judge FW reported last RSSI > roaming
Low rssi and not less than 20db of host cached RSSI to avoid
some false alarm such as normal DUT roll in/out roaming.
Change-Id: I5d8ec9e9d4f8a44178b113d370799fe2bc0373fb
CRs-Fixed: 2841481
Print is logged on rx packet deliver failure with
no relevant info since the skb is already freed.
Fix is to not log info on packet deliver to stack
failure.
Change-Id: I8f91a14030c76907d60e95ccbd19b600938ace90
CRs-Fixed: 2849093
Reduce excessive logging for roaming path to reduce latency.
Also remove function and line prints in roam debug related
logging.
Change-Id: Ida6fc55886c944126720f8bdd4b944765426ccc6
CRs-Fixed: 2847773
Subscribe for Tx data wdi event and process Rx data packets
and post into mon thread for packet capture mode
Change-Id: I1a2930110bebc152db32cb2c1f1bc1120fc29755
CRs-Fixed: 2845597
Subscribe for Tx data wdi event and process Tx data packets
and post into mon thread for packet capture mode
Change-Id: Id4c231ce8f32c45f579289b37cb810581c6ab31b
CRs-Fixed: 2845593
Acquire connection list lock in policy mgr before update the
entry. The "conn_index" maybe changed for a connection entry
if other connection is up or down.
Fix by acquire connection to protect the whole "update" operation.
Change-Id: I91e82e74884ef32e83e0c4105e88bafe8d99db3d
CRs-Fixed: 2848209
Configure TWT SAP PDEV count using CONFIG_WLAN_TWT_SAP_PDEV_COUNT
and SAP STA count CONFIG_WLAN_TWT_SAP_STA_COUNT for QCA6490
Change-Id: I74ef054d9cb64ccf66d7e1e788a8cc75aec70cb9
CRs-Fixed: 2843660
In moselle, the runtime suspend and wow resume sync logic has
been added without any condition, since hastings is doing APPS
side PCI bus suspend which cannot be reverted on suspend failure,
so doing this sync logic only if wake irq type is CE interrupt.
Change-Id: I07dc5a99d0661fe1ef81e7a46e7053244edf8eb6
CRs-Fixed: 2851261
When runtime power management is enabled, until the system is fully
resumed, we do not post any message to CE, instead they will be queued
in HTC. Once the device is fully resumed, all HTT messages in the queues
will be downloaded to CE at once. In some corner cases, it is found that
too many FSE caches flush messages getting queued during the runtime
resume; once the device is fully resumed, all these would be downloaded
to the FW/HW at once causing unintended crashes.
Do not post FSE cache flush messages when the device is resuming from
runtime suspend to avoid this problem.
Change-Id: Iaa7a25e6f84ef4ac9c3cdf6a5c052538b142ea3f
CRs-Fixed: 2839431
Currently, host driver is checking for concurrency while handling
the pre_cac request. pre_cac adapter won't be deleted until SAP is
stopped. As a result the second pre cac request for the same SAP
will be dropped due to this concurrency check.
To avoid this, Don't check for pre cac concurrency if the pre cac
adapter is already exists.
Change-Id: I780c6310cf819da1a2f5c7c93590ccb1b544e7a4
CRs-Fixed: 2848736
In pmo_core_configure_dynamic_wake_events vdev reference is acquired
and its not released leading to the reference leak, leading to
vdev destroy timeout.
Release the vdev reference to resolve the issue.
Change-Id: Idd3bcb366f211e037ede278c91d6bcefd4165651
CRs-Fixed: 2850076
Event WLAN_IF_MGR_EV_AP_START_BSS delivery will trigger roam disable/
enable. That will involve lots of wmi command to set roaming parameters
to firmware. When the AP is "started" state, the
wlan_hdd_cfg80211_start_bss will be called to update AP (GO) IE and
wlansap_start_bss will be skipped. In this case, we don't
need to deliver WLAN_IF_MGR_EV_AP_START_BSS event.
Change-Id: I801fd7a5eaf7b97b2c74930c9e4088db83c86a09
CRs-Fixed: 2847224
In the issue scenario, roaming is triggered due to NUD_FAILED
event and nud state is set to NONE once roaming is completed.
NUD_FAILED events could be received without any NUD_PROBE
INCOMPLETE events post this roaming and these nud failures
are not honored due to which further roaming due to NUD_FAILURE
won't be triggered.
Fix is to set nud state to PROBE explicity on receiving
NUD_FAILED event post roaming.
Change-Id: Ib34b82f478263eb9664112a25f2d1f8bd858f5dc
CRs-Fixed: 2837825
Add entries to pre-allocate memory region for
recording datapath rx ring history.
Change-Id: Iffac199c48a9638c94d8568bbc7567bf214ffcc2
CRs-Fixed: 2847548
In populate_dot11f_chan_switch_wrapper() host uses channel number to
prepare tx_power_env IE. As channel number is input to
populate_dot11f_tx_power_env(), tx_power_env IE gets wrong values of
max tx power constraints.
Hence input sw_target_freq to populate_dot11f_tx_power_env().
Change-Id: If3112f9e68bdb57cbfd3073ed25f3dcf4f9750d7
CRs-Fixed: 2842552
Currently for FISA aggregated RX frame, one skb will contain 2~16
RX msdu, if only count 1 RX msdu into stats, BW vote is not right
that even if RX T-put > 1 Gbps, wlan only vote 4(high), this can not
satisfy the vote requirement for peak T-put > 2 Gbps which should be
5(very high) which then degrade the T-put.
Fix RX packets stats correctly for aggregated RX frame.
Change-Id: Idd0cee1b68555dedad49025c03a13a929ec2af1c
CRs-Fixed: 2838667
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
In moselle, once wow enabled there is a possibility that wow wake
interrupt can be fired from FW during runtime suspend in progress
in host, this will introduce a race between runtime suspend and
resume, so adding a synchronization between runtime suspend and
wow triggered runtime resume.
Change-Id: I19a4d70f47d5c202d0ba291c3edc8a260690f434
CRs-Fixed: 2845670
Currently driver does not update he and ht rate flags correctly
in wma as rate flags should include all the subsets of the
lower rate sets, which is not the case today and driver only
updates the higher rate flag. Because of which it leads to
invalid computation of txrate at the kernel.
To address this issue, update he and ht rate flags correctly in
wma.
change-Id: I6ec68af1f75650990384efbd61536042329665b2
CRs-Fixed: 2837245
