diff options
author | vamsi krishna <vamsin@codeaurora.org> | 2019-02-01 18:34:51 +0530 |
---|---|---|
committer | Johannes Berg <johannes.berg@intel.com> | 2019-04-08 13:44:40 +0200 |
commit | 1e1b11b6a1111cd9e8af1fd6ccda270a9fa3eacf (patch) | |
tree | b408dc4efaf458bf15b779f779bc72d37fcd0ad4 /drivers/misc/aspeed-lpc-snoop.c | |
parent | d39f3b4f33d245a08a7296a04bab80bd52466f58 (diff) | |
download | linux-stable-1e1b11b6a1111cd9e8af1fd6ccda270a9fa3eacf.tar.gz linux-stable-1e1b11b6a1111cd9e8af1fd6ccda270a9fa3eacf.tar.bz2 linux-stable-1e1b11b6a1111cd9e8af1fd6ccda270a9fa3eacf.zip |
nl80211/cfg80211: Specify band specific min RSSI thresholds with sched scan
This commit adds the support to specify the RSSI thresholds per
band for each match set. This enhances the current behavior which
specifies a single rssi_threshold across all the bands by
introducing the rssi_threshold_per_band. These per band rssi
thresholds are referred through NL80211_BAND_* (enum nl80211_band)
variables as attribute types. Such attributes/values per each
band are nested through NL80211_ATTR_SCHED_SCAN_MIN_RSSI.
These band specific rssi thresholds shall take precedence over
the current rssi_thold per match set.
Drivers indicate this support through
%NL80211_EXT_FEATURE_SCHED_SCAN_BAND_SPECIFIC_RSSI_THOLD.
These per band rssi attributes/values does not specify
"default RSSI filter" as done by
NL80211_SCHED_SCAN_MATCH_ATTR_RSSI to stay backward compatible.
That said, these per band rssi values have to be specified for
the corresponding matchset.
Signed-off-by: vamsi krishna <vamsin@codeaurora.org>
Signed-off-by: Srinivas Dasari <dasaris@codeaurora.org>
[rebase on refactoring, add policy]
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'drivers/misc/aspeed-lpc-snoop.c')
0 files changed, 0 insertions, 0 deletions