At present, there is not check while calling multipass processing
and hence no packet gets dropped.
Adding check will drop packet in case of returning return type as
false. Hence modified return type as true so that no packet gets
dropped and existing flow doesn't break.
Change-Id: I49089f155b1b78adb533ca23f3b0f3cad9543135
CRs-Fixed: 2599782
Add WMI change to support extraction of consolidated multi vdev
response handling from TLV.
Change-Id: I5b9697b130ec38ac64de5a63ad8e491b9b786604
CRs-Fixed: 2601729
Add change to support consolidated multi vdev restart response
handling for non-TLV based platforms.
Change-Id: I58445fb66465b987906d23c079813b010976b380
CRs-Fixed: 2593073
1. In CFR RCC mode, when ucode aborts DMA of CFR data, 2 (or)
more PPDU status TLVs are likely to have same phy_addr+cookie in
RX location TLV, so the host will be flushing out the older PPDU
status TLV events instead of DBR events in LUT table,
since DBR events signify the actual DMA completion.
2. Same fix has been made for LUT entry ageout logic.
Change-Id: Ifc0717e97d21ba3463cc2f5ceb2f22a657177002
Earlier, CFR's LUT was dumped when difference between dbr count
and release count is greater than 1. This might be agrressive.
Modified the condition to reflect the worst case where LUT has
no empty entry.
Change-Id: I010431b446ddb66364505f0c8d9a70dd181eb8b1
This changes removes references to dp_handle in CFR component, to ensure
consistency with FR#56622.
Change-Id: I3539e958ed3fe4ef68f22adf473349b5639cb4b1
PHY may not be able to capture the CFR data in certain cases.
Ucode will update the reason due to which CFR capture did not
happen in PHYRX_PKT_END TLV.
Channel capture status -
0 - CAPTURE_IDLE
1 - CAPTURE_BUSY
2 - CAPTURE_ACTIVE
3 - CAPTURE_NO_BUFFER
Originally, ucode updated channel capture status only for PPDUs,
for which PHY was able to capture CFR data successfully. Ucode is
making a change to report channel capture status in PPDUs for which
PHY was unable to capture CFR data.
Re-positioning the counters in host to handle this new change in
ucode.
Change-Id: I915fe7c4969649754936cab624343e044b397a0c
Supported dynamic HW mode switches:
DBS (full band 5G and 2G) <-> DBS_SBS (low band 5G, high band 5G and 2G)
Description of the changes:
1. NOL conversion:
a. Introduce a temporary NOL list copy structure in DFS psoc obj.
b. When mode switch is triggered:
i. Stop the NOL timers and clear the data, to avoid processing NOL
expiry during mode switch.
ii. Allocate the psoc NOL copy for the target num_radios.
iii. Store the NOL data of each radio to the target pdev ID
(pdev ID after mode switch) in the psoc NOL copy,
using a unified mux/demux API.
c. After mode switch is completed:
i. Resume NOL by re-initializing the list from the temporary psoc
copy.
ii. Free the psoc copy after mode switch is complete.
iii. Note: changes are made to support pause and resume of NOL,
increasing NOL timeout by a few milliseconds.
2. PreCAC list conversion:
a. When mode switch is triggered:
i. Stop the existing preCAC timer and send ADFS abort command to FW.
b. When mode switch is completed:
i. Unify/separate the preCAC list if the target mode is DBS/DBS_SBS
respectively, using a single API.
ii. Start ADFS again.
3. Radar detection lock:
a. While detecting radar, acquire a lock to avoid handling user triggered
mode_switch during this process. Release the lock once radar
processing is completed and CSA start is triggered.
4. Radar detection/CAC completion defer during mode switch:
a. While detecting radar or CAC completion, check if mode switch is
in progress. If yes, wait for mode switch to complete before
handling the events.
b. Note: Precedence is Radar over CAC, i.e., if CAC processing is waiting
and radar is received, CAC completion is no longer handled.
CRs-Fixed: 2535058
Change-Id: I55e03dae9da994c21b1aafe7b7686f5299221a40
Framework to accumulate RCC configurations until user issues commit
command. Once commit command is issued, all the gathered configurations
are sent to FW through WMI fixed and variable TLVs.
Change-Id: I84fec42d22a3b4eceb710b72d89a7c3047fed1f6
CRs-Fixed: 2582833
Channel Frequency Response(CFR) captures FFT bins corresponding to a PPDU
received and this is relayed to user space application along with
additional information about the PPDU gathered in the host. Usecases of
this feature include location sensing, motion detection.
Change-Id: If0da492bc1fcc0fc2b6e42339c56f9a54ee813f7
CRs-Fixed: 2541307
Equivalent changes in component dev data path APIs
implementation for changes in cmn_ops interface APIs.
Change-Id: I1d9c43607bfa699dded771fe9aea87f4ec5a70b9
Block ack and ack frame is composed and sent to up
layer after a unicast packet to AP is received for
tx capture feature
Change-Id: I512519de7eaf4f524825b854b33dedc4caf90e0e
before sending tx capture data frame to stack
rts_success flag is checked on set we send rts and cts dummy frames
before data frame.
Change-Id: Id3dccf5c03b05ff381eb595d7807385afb78d462
Bar frames without payload are generated for tx capture.
added a generic function to generate dummy frames
for type CTL and MGT into function.
Change-Id: I4408b1b023eeaefa17a6e121cda6a9a64d025202
Airtime Management (ATM) Groups and Rules WMI support on Hawkeye.
This change will add WMI TLV support for Hawkeye.
CRs-Fixed: 2573295
Change-Id: I2f4cc132fd3568c4db5f3b70dcb05c1808dfd4a2
On sending STOP req, RESTART pending, RESTART send flags are being cleared.
This is already being done before moving out of RESTART_PROGRESS sub state,
so avoiding it.
Change-Id: If8b358eb83571e11d6e0d3bcbedcf833894bf0d6
CRs-Fixed: 2578106
Restricted 80+80 MHz feature is not supported for pre-lithium chipsets.
Therefore set restricted 80+80 as unavailable.
Change-Id: I80603ea814d24a29588ec5d62a8ac2d0ac3b86ba
CRs-Fixed: 2580513
