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
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
Add check to know if tid is still in initialized state while
delivering a ppdu with flush bit set.
Change-Id: I6f0fbbdb616ba4b6c98787d389b7bf16d6c5f165
The current debug print is not sufficient to look at
peer, tid. So enhanced current print
CRs-Fixed: 2794519
Change-Id: If531f1892cfc53c308b1913891a54f4a9350d02c
Implement a new driver module for Mirrored stream classification
signalling(MSCS) feature. This module which register to NSS MSCS client
to provide callback for peer lookup and priority update based on MSCS
parameters associated with a peer
Change-Id: I7aa465446cb22f0198459193fa04dd66fc903cc7
The following sanity check for processing the radar on agile channel
(dfs_process_radar_ind_on_agile_chan) is already present in the caller,
(dfs_process_radar_ind) where the radar action is classified based on
radar found params:
i) is dfs agile precac enabled?
ii) is rcac enabled?
iii) is a valid agile channel configured?
These checks are not enough when radar is detected on Zero Wait DFS
channel. But this is taken care in the parent function
Remove these redundant checks as they are already present in the parent
function flow dfs_is_radarsource_agile().
CRs-Fixed: 2764058
Change-Id: Ia67d6ee28f5f04e149c1049bd5642f04e6a4bc70
If user configured frequency is provided for RCAC, instead of using
the current channel width to determine the channel, use the mapped
agile channel width instead. This is because, incases of the current
channel width being 165MHz for example, agile channel can only be
160MHz (indicated by the agile_chwidth variable).
Change-Id: I4634a4baf25efa3341ed0232ccf5c55b300bbbe7
The radar parameter received from FW for Pine is based on the 160MHz
channel center. In Host a preprocessing to convert this radar parameters
based on 160MHz channel center into parameters based on 80MHz channel
center is done. This translation is present for the current channel but is
absent for the agile channel.
Also, for the 165MHz agile channel, the radar parameters are always sent
to host based on the left 80MHz center frequency 5690MHz.
Introduce a radar parameter translation function for 160/165MHz Agile
channel such that
1) If the radar hit frequency is left to the center of 160MHz center
frequency, then the segment id should be primary segment. The offset
frequeny that was with respect to the 160MHz channel center should be
converted into offset frequency based on the left 80MHz center by adding
40MHz on the offset received.
2) If the radar hit frequency is right to the center of 160MHz center
frequency, then the segment id should besecondary segment. The offset
frequeny that was with respect to the 160MHz channel center should be
converted offset frequency based on the right 80MHz center by subtracting
40MHz on the offset received.
3) If the radar hit frequency is on the left 80MHz segment of the
165MHz channel then do nothing because, the radar paramters are sent by
FW with respect to the left 80MHz center frequency of the 165MHz channel.
4) If the radar hit frequency is on the right 80MHz segment of the
165MHz channel then the segment id should be secondary segment id and the
offset should be converted to be based on the right 80MHz center frequency
5775MHz by subtracting 85MHz.
Change-Id: I47471e65c5831c0aa9c2c36338021a55d4dc7c7b
CRs-Fixed: 2784515
tx capture does not capture mpdu, which missed due to
block ack failure. with subsequent retries it recieve block ack for
all the previous transmitted mpdu in a ppdu was handled.
Change-Id: I23d1bfd7ba05edaec934379fbc036b164a45ceb6
