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
Converges EXPORT_SYMBOL() to qdf_export_symbol(),
this ensures easy enabling and disabling of exports
Change-Id: I5724a618c9dff7a30b9d314906fbabca943bded8
While configuring the precac timeout as part of starting the agile
engine, the timeout value sent to FW and HOST timer were both equal,
resulting in two separate timeout.
1. Zero second timeout due to OCAC complete event from FW.
2. preCAC timer timeout.
Because of these timeouts, same channel is marked as OCAC complete
twice. To avoid this, increase the HOST timer timeout value by
2 seconds.
Change-Id: I9b649b5c783df962df2b8410691ee00d1abb4a9d
CRs-Fixed: 2556726
Introduce a phyerror sample analogous to the phyerrors given by FW and
store itin the text file. Read the text file and Inject this phyerror to
the DFS algorithm.
Change-Id: Iff33b6554911e4f3e8101cb81df5c500cd96f041
CRs-Fixed: 2484584
The IEEE channel numbers in the 6GHz band overlap with the IEEE channel
numbers in 2.4GHz, 4.9GHz (e.g. Channel number 1) and 5GHz
(e.g. Channel number 149). Currently many APIs in Agile DFS (ADFS),
have channel number as a parameter. This leads to the channel number
collision. To overcome this, new APIs with channel center frequency
(in units of megahertz or MHz) as a parameter are created, as
channel center frequency is unique for 2.4 GHz, 4.9 GHz, 5GHz,
and 6GHz channels.
Each new API performs the same function as its old counterpart.
For example dfs_find_cac_status_for_chan() and
dfs_find_cac_status_for_chan_for_freq() perform the same operation. The
difference in the latter, is that the channel center frequency is given
as an input parameter instead of IEEE channel number, and the function
body is modified to suit channel center frequency.
The new channel frequency based APIs are placed under the macro
"CONFIG_CHAN_FREQ_API" and the existing channel number based APIs are
placed under the macro "CONFIG_CHAN_NUM_API". The APIs under the macro
CONFIG_CHAN_NUM_API will be removed, when when all the references to
the APIs are removed.
CRs-Fixed: 2526360
Change-Id: Icff94f518af3621b039f059f1409106a5639ed8b
Populate MAC clock rate for non-TLV chipsets. This is required in
order to convert CCA cycle counts to time for standard cfg80211 iw
survey functionality.
Change-Id: I6f109b3bf225ab44634261d6afda7737230827c8
CRs-Fixed: 2543004
There seems to be a case where difference between DBR event count
and release count for CFR events is more than 1, which will dump
CFR's look-up-table. As the exact reason for this is not known yet,
we are reducing the log level for these prints to not be enabled
by default
Change-Id: I503f6423f08e6faa84b45747a28ec1a7de4724fc
Report CFR failed status to application by sending CFR header with
error status.
Change-Id: I67e370bbbd8294a14c32567922861a0b5226b0ea
CRs-Fixed: 2538596
For new CFR captures with AoA data, Meta data version is 2.
Updating meta data version to 2.
CRs-Fixed: 2537866
Change-Id: I4c6cb9775e5a9760630b1f28d61fb4bdfd084c6c
Include host generated management and also update
phy information for control and mgmt indications from
FW when Tx capture is enabled.
Change-Id: Icbc0b175c73b6eab0bb6e35fa157bfce92927d24
As part of the ETSI preCAC feature, every 20MHz channel that is CACed
and not in NOL is maintained in a list which is then checked during every
channel switch for CAC reuse (avoiding CAC).
With the introduction of preCAC list (Binary Search Forest) for
20, 40 and 80MHz channels which also includes the current channel CAC
information, the ETSI preCAC list has become redundant.
Remove all APIs and changes that support the redundant ETSI preCAC list.
Change-Id: I76656807bc117af1f6909160ade86ae13d390f1a
CRs-Fixed: 2484864
In Tx capture feature, Addr 3 is wrongly populated
with peer mac. Add fix to pick correct SA from
ethernet frame and use in wireless hdr.
Change-Id: I457c3118a1e8e5e7aace4e784e2978e89dda2eda
CRs-Fixed:2532324
After every wifi up/down or load/unload, it is expected that
cfr enabled entries should be reset. Earlier, associated clients'
entires are cleared by FW. Unassociated entries are maintained by
host and were not cleared. This change clears them properly at
cfr_pdev_open level
Change-Id: I2dd7ce861901ccca72bc987c2f91677a481d401e
CRs-Fixed: 2531961
