cfg80211: clarify DFS / CAC case for the new NO-IR flag
PATCH 1/1 cfg80211: clarify DFS / CAC case for the new NO-IR flag
Now that the no-ibss and passive-scan flags are bundled together its a lot easier to deal with the case of when we support DFS. If DFS is supported on the wiphy and if the Channel availability check (CAC) has been cleared on the channel (dfs_state is NL80211_DFS_AVAILABLE) we can ignore the no-ir flag.
This simplifies the paranoid requirement of bundling together DFS and NO-IR cases by placing onus on the DFS implementation. If code paths also want to reuse knowledge from DFS state machines they must also ensure that they always look at and monitor the dfs_state.
---
This depends on the 2 series I posted just before, the ath driver updates and the wlan driver merge of consolidating flags.
include/net/cfg80211.h | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
include/net/cfg80211.h +5 -1
@@ -92,7 +92,11 @@ enum ieee80211_band {* * @IEEE80211_CHAN_DISABLED: This channel is disabled. * @IEEE80211_CHAN_NO_IR: do not initiate radiation, this includes -* sending probe requests or beaconing. +* sending probe requests or beaconing. Channels that have +* %IEEE80211_CHAN_RADAR enabled can ignore this flag if +* and only if the Channel availability check (CAC) has +* been cleared on it, that is when the channel's dfs_state +* is %NL80211_DFS_AVAILABLE. * @IEEE80211_CHAN_RADAR: Radar detection is required on this channel. * @IEEE80211_CHAN_NO_HT40PLUS: extension channel above this channel * is not permitted.
Signature · 1 line
1.8.4.rc3
Johannes Berg
maintainerQuoted 7 lines · Luis R. Rodriguez
Now that the no-ibss and passive-scan flags are bundled together its a lot easier to deal with the case of when we support DFS. If DFS is supported on the wiphy and if the Channel availability check (CAC) has been cleared on the channel (
dfs_stateisNL80211_DFS_AVAILABLE) we can ignore the no-ir flag.
Quoted 5 lines
This simplifies the paranoid requirement of bundling together DFS and NO-IR cases by placing onus on the DFS implementation. If code paths also want to reuse knowledge from DFS state machines they must also ensure that they always look at and monitor the
dfs_state.
Please resend this as part of the other series when my comment there is sorted out. (Unless nothing is needed, in which case just remind me to pick this up if I forget)
johannes