As part of the componentization of channel lists across WIN
components, the existing version of channel list in WIN umac is
removed. Introduce APIs in the regulatory that provide the
required information directly from the regulatory
channel lists.
Introduce the following APIs:
1. wlan_reg_get_txpow_ant_gain
To get the txpower and antenna gain specified in the regulatory,
for a given channel.
2. wlan_reg_get_chan_flags
To get the channel flags (if channel DFS for example), from
regulatory for the given channel.
3. wlan_reg_get_max_phymode_and_chwidth
To get the maximum 80211 mode and channel width supported
by the channel in the given regulatory.
4. wlan_reg_is_phymode_chwidth_allowed
To check if the given 80211 mode and channel width is supported
by the channel in the given regulatory.
5. reg_update_max_phymode_chwidth_for_pdev
To update the maximum 80211 mode and channel width for the
regulatory, inside regulatory object.
6. reg_modify_chan_list_for_max_chwidth
Update the regulatory channel list with maximum bandwidth
for each channel based on the availability of it's
adjacent channels.
Change-Id: Idb390c10d8901d9e21d4642481168704d7e36333
Limit DIAG queue length to avoid memory lockup.
In use-cases where all the cores are busy executing interrupt
handlers and tasklets, work/processes might starve.
To avoid memory being locked up in wmi buf queue which is processed
in work ctxt, it is essential to limit the queue length.
Since highest proportion of the WMI events processed in work ctxt
are FW diag events, to avoid memory lock up, drop FW diag events
when queue length threshold is reached.
Change-Id: I1982eff5bea6b49c0e0b0987c439d2b7af04922e
CRs-Fixed: 2785768
Extend the current check for action frames in tx capture
to include more types of FW generated action frames.
This change adds a generic function to check where action
frames are generated that is easily extended to account
for more types in the future.
Change-Id: I23bb37c5a81b02d2c095060bac909298d1b2283f
CRs-Fixed: 2807802
Add command support to meet the customer use case for switching
channel from 5Ghz to 6Ghz in wideband radio. The switch should
happen conforming to target-band multi-bss mode requirement which
is EMA in 6Ghz
Change-Id: Id55577eb7d0b3424e3b07bcfec054ce9a6556c26
The earlier WAR was not handling a corner case, where
ba_size equal to mpdu_tried_ucast -1.
This fix updates the check to handle it.
CRs-Fixed: 2813082
Change-Id: Ib69f8232e40ee31bc4a4a2b35ec9e8917195d123
When radar is detected on a zero-wait-precac channel, the precac channel
changes but the phyerror buffers for the previous precac channel keep
coming, affecting the newly configured precac channel and creating false
detects.
Consider, a Cascade AP operating in home channel 36VHT80 and the precac
channel is 52VHT80. When the radar is injected on channel 52VHT80, the
precac channel changes to the next precac channel 100VHT80 but still
continues to receive the queued phyerror buffers, causing radar detects
on channel 100VHT80(false detects with respect to channel 100VHT80).
Disable radar detection after radar got detected on the precac channel.
CRs-Fixed: 2812335
Change-Id: I1e06c53f00e596d9142f3aeb25a00b9da088538b
Change log level of print from qdf_info to dp_info during
rate stats flush to avoid console flooding and backpressure issue.
Change-Id: Ic8a067f989047be1a223af83a2d6d0485dd10ebd
Pass BTM Query, Response and Neighbor Report Request
to Hostapd if corresponding flag is enabled. By default
handling will be in driver.
Change-Id: Ic7fc1acf26329a48695b3daa40afe04c9e2040b8
In independent repeater scenario where STA vdev takes longer for
auth/assoc, and the AP vdevs are waiting on restart request may lead
to restart timeout.
Hence increase restart timeout to 20s which is higher than auth/assoc
timeout.
Change-Id: I5d2a0859e368feda4e1c6d3824eefdbc248b9bac
Add WMI support to extract data received from fw
for WMI_PEER_CREATE_CONF_EVENTID event id.
Change-Id: Ifcf4c3e2f21be1433b96079405650a3448e0652e
CRs-Fixed: 2797202
The loop counter is not incremented in an error path where the peer rate
stats ctx is NULL. As a result, if this error path is exercised,
backpressure is seen on the monitor status ring. Fix it.
CRs-Fixed: 2798226
Change-Id: Iaffc14ad14fb29909459e395c0dfd6811c42ebc1
Add appropriate check to kickout directly associated peer
when it roams to another AP and reachable via TA peer.
Change-Id: I3e7cc0f1f4e4aa3e05fd7b7e823471978d07a64c
CRS-Fixed: 2801038
Add new command to check if NSS WiFi offload is enabled
or disabled
1. iwpriv wifiX g_nss_wifi_ol
2. cfg80211tool wifiX g_nss_wifi_ol
Change-Id: I0486874bbb794bbcc239f268833176dca8826b5b
For a 16-MB profile, while insmoding "umac.ko" unknown symbol error for
function "dfs_translate_radar_params_for_agile_chan" is seen.
The actual definition of function
"dfs_translate_radar_params_for_agile_chan" is present in the
dfs_zero_cac.c which is not compiled for a 16-MB profile. Therefore,
the unknown symbol error is seen.
Add ADFS compile-time macros
QCA_SUPPORT_AGILE_DFS and QCA_SUPPORT_ADFS_RCAC to the declaration of the
ADFS specific function dfs_translate_radar_params_for_agile_chan().
As the macros are not present in 16-MB profile, the function becomes an
empty function in the zero_cac.h and definition of the function
dfs_translate_radar_params_for_agile_chan() is present (though empty)
in the umac.ko.
Change-Id: I873231c703796c4ff17ec9a15fe2df7ddde1b8dc
CRs-Fixed: 2801858
It is found that mpdu_tried_ucast is less than last ba bitmap set,
this is leading inconsistency with mpdus[] array and failed_bitmap.
To address this, on failed_bitmap prep, if mpdu_tried_ucast is less
than last ba bit set, then mpdu_tried_ucast is updated with last ba
bit set.
CRs-Fixed: 2793967
Change-Id: I381b462d0418527dd11ca2c8ae3dc4c8d4bfdba8
1. Remove the fdb entry linear search.
2. Store the station vap pointers.
3. Add or refresh the secondary Client bridge entries
to not make them get expired even though traffic is bypassing
the bridge.
Change-Id: I11a7883d0437794ad8afeb24fc94d77223cf3ad3
