With the current implementation dfs->dfs_soc_obj was initialized in
function dfs_agile_soc_obj_init under the macro QCA_SUPPORT_AGILE_DFS
and ATH_SUPPORT_ZERO_CAC_DFS both of which are disabled for the low
memory profiles. Remove the initialization from here and unconditionally
initialize it in wlan_dfs_pdev_obj_create_notification.
Change-Id: I207ed4e7d5cb42100e5bf1cbf55cdd9de13f35b8
Peer wlanstats context was accessed directly
without any protection, if peer was deleted
there was no way to know if PPDU cookie holds
correct wlanstats ctx
Hence to protect the peer wlanstats ctx access
it using CDP API using stats context protection
CRs-Fixed: 2740231
Change-Id: I9b07970c691099f3c9b0175d550508b50db9ac8a
Currently there is only a provision to enable
and disable RDK stats with enable_rdk_stats
INI configuration
Since there are new set of statistic metrics added
as part of RDK stats, add version information into
CFG INI configuration such as
0. For disabling stats (By default)
1. For enabling peer rate stats only
2. For enabling peer link metrics only
3. For enabling both statistics
This is done to avoid unncessary CPU consumption
and memory consumption for each peer, depending on
the requirement the version can be enabled
CRs-Fixed: 2740231
Change-Id: I1cfd8c75dd4f3236a5b07263573fd5ddbe1dc1c3
Add 'puncture_band' commmand support to configure the Punctured band
setting for AP. The command takes a bitmap argument, where each
bit corresponds to a 20MHz band. For instance for AP configured
for 80MHz BW the least 4 bits will be valid bits.
Change-Id: Ic3ce03776477c63af8c1d735a7eacd5aa19dd51f
CRs-fixed: 2749137
Adding new metrics to existing RDK Plume statistics
PHY Metrics Tx
1. phy_rate_actual_su - Single User Rate
2. phy_rate_actual_mu - Multi User Rate
3. ofdma_usage - OFDMA Usage count
4. mu_mimo_usage - MU MIMO Usage count
5. bw_usage_avg - Average BW
6. bw_usage_max - Max BW Ratio to total PPDUs
7. pkt_error_rate(mpdu) - MPDU packet error rate
8. num_ppdus - Number of PPDUs
9. num_bytes - Number of PPDU bytes
PHY Metrics Rx
1. phy_rate_actual_su - Single User Rate
2. phy_rate_actual_mu - Multi User Rate
3. ofdma_usage - OFDMA Usage count
4. mu_mimo_usage - MU MIMO Usage count
5. bw_usage_avg - Average BW
6. bw_usage_max - Max BW Ratio to total PPDUs
7. pkt_error_rate(mpdu) - MPDU packet error rate
8. num_ppdus - Number of PPDUs
9. num_bytes - Number of PPDU bytes
RSSI
1. su_rssi - Single user Rx RSSI
2. ack_rssi - ACK RSSI
CRs-Fixed: 2740231
Change-Id: Ie62157195d87f61640aa7bc65b2f02f629ff195d
Required for Instrumentation of code using cc_func() to find errors
and trace function calls.
This supports printing dump of functions that are called during
test case execution for CBT.
Change-Id: Idbf5e84deb8538dc85dadcbca9ad07bb57a67db9
Remove peer pointer in AST entry and store peer_id instead
to avoid access of peer memory without taking reference
Change-Id: I1e9c2a6880b3582866b821bf56a8400e056665f2
The radar found action on a agile channel is a WIN specific action. It was
combined with the current channel radar detection making the function huge
and difficult to read.
Separate the WIN specific agile radar action and define in it as WIN
specific.
Change-Id: I79ed61ae80a2870dff9775b9435069c50584ca83
CRs-fixed: 2738015
Adds support to enable/disable Mirrored Streaming
Classification Service Procedure in vap level.
Change-Id: I2e27f0be294e1792ba9a6ad7a0354515c5ee6cc0
CRs-Fixed: 2687735
In few scenarios,dp_get_pdev_lmac_id shall returns null.
To avoid this added a null pointer check to avoid the dereference issues.
Change-Id: I5a859c81295a49afd3fc083c6611eceec414d2ca
In case of a current channel being a 5GHz DFS channel, a channel change
may be triggered by a radar detection. The next channel is automatically
selected by a random channel selection algorithm in this case. However,
if the current channel is a 6GHz channel and we need to switch to a 5GHz
channel then 5GHz channel should be provided a user or another channel
selection algorithm. At the time, when the device is starting its
operation on a 6GHz channel , the next 5GHz channel that a user
(or another another channel selection algorithm) is going to select
is unknown. Therefore, the probability that the next channel selected
by a user (or another channel selection algorithm) will match the RCAC
channel returned by random channel selection, is very low. Therefore,
do not select a random channel for RCAC if the current operating channel
is a 6G channel for now.
Change-Id: I9aef64cea1d442fc31b2314da08baba7769650f2 has the following
change :
The macro WLAN_IS_CHAN_MODE_x(_c) checked if mode is 'x' as well as if
the channel was a 5G channel. However with wideband changes this macro
will return true if mode is 'x' for both 5G and 6G channels. Hence adding
a separate 5G check for functions where the channel must be a 5G channel.
With WLAN_IS_CHAN_MODE_x(_c) now a 6G channel will pass
the checks in dfs_is_precac_done which would cause regression. Hence a
5G check has been added to prevent this.
Change-Id: Iee5e965f0bc99565cb5ea77d88998d5530f24153
For the 16M low memory profile a few feature macros were disabled which
led to unavailability of a few APIs.
Add empty definitions for these APIs when the corresponding feature
macros are disabled.
Change-Id: I1f7790196ae8383eac40f5869992fd06ede3e5dc
Introduce enums for set DFS postNOL frequency and mode and add
the corresponding members in the set and get command structure.
Change-Id: I3e25ee3aaf0c165a2923667a3210f2cc8af0af4a
