linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: johannes@sipsolutions.net
Cc: janusz.dziedzic@tieto.com, j@w1.fi, sunitb@qca.qualcomm.com,
	rsunki@qca.qualcomm.com, linux-wireless@vger.kernel.org,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [RFC 0/5] cfg80211: regulatory quiescing and exporting DFS regions
Date: Wed, 13 Nov 2013 19:12:54 +0100	[thread overview]
Message-ID: <1384366379-25301-1-git-send-email-mcgrof@do-not-panic.com> (raw)

This series depends on my last posted series.

This set tries to address some issues I was with checking for DFS region
support on the cfg80211 path for starting radar detection. Apart from
checking for the DFS region when we get a request to start DFS radar
detection we should always check the DFS region also when we want to
use a mode of operation that requires DFS support in the kernel. IBSS
has a mode of operation, when NL80211_ATTR_HANDLE_DFS is set, which
should be taken into consideration for DFS support. My patch 5 titled
"cfg80211: DFS check dfs_region before usage" really is incomplete
and should check for NL80211_ATTR_HANDLE_DFS on IBSS wdevs when set
to make the appropriate exception.

While at it I considered the corner cases of changing regulatory domains,
this pushed me to add regulatory quiescing support. This is particularly
important when we switch regulatory domains and the DFS region changes but
should nevertheless still be done even in other cases. I think we should
also extend the IBSS NL80211_ATTR_HANDLE_DFS case to require newer
implementations to send their supported DFS regions, otherwise we assume
userespace is doing the right thing. I think we can take care of that better
in kernel space.

Janusz, please test, and likely feel free to take on the last patch.
We may need help from Johannes on the rtnl lock question now required
for checks on enabling beacon operation.

Jouni, thoughts on the approach? Sunit, Rakesh?

Luis R. Rodriguez (5):
  cfg80211: pass the wdev on the country IE regulatory hint
  cfg80211: make cfg80211_leave_all() available outside of sysfs
  cfg80211: add regulatory quiescing support
  cfg80211: add DFS region capability support
  cfg80211: DFS check dfs_region before usage

 include/net/cfg80211.h       | 57 +++++++++++++++++++++++++++++++++++++++++++
 include/net/regulatory.h     |  4 +++
 include/uapi/linux/nl80211.h | 21 +++++++++++++++-
 net/wireless/chan.c          |  8 ++++++
 net/wireless/core.c          | 47 +++++++++++++++++++++++++++++++++++
 net/wireless/core.h          |  2 ++
 net/wireless/nl80211.c       | 15 ++++++++++++
 net/wireless/reg.c           | 58 +++++++++++++++++++++++++++++++++++++++++++-
 net/wireless/reg.h           | 13 +++++-----
 net/wireless/sme.c           |  2 +-
 net/wireless/sysfs.c         |  8 ------
 11 files changed, 218 insertions(+), 17 deletions(-)

-- 
1.8.4.rc3


             reply	other threads:[~2013-11-13 18:13 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 18:12 Luis R. Rodriguez [this message]
2013-11-13 18:12 ` [RFC 1/5] cfg80211: pass the wdev on the country IE regulatory hint Luis R. Rodriguez
2013-11-13 21:20   ` Johannes Berg
2013-11-14 14:05     ` Luis R. Rodriguez
2013-11-14 14:02       ` Johannes Berg
2013-11-14 15:12         ` Luis R. Rodriguez
2013-11-14 15:05           ` Johannes Berg
2013-11-14 15:21             ` Luis R. Rodriguez
2013-11-15 16:28               ` Luis R. Rodriguez
2013-11-13 18:12 ` [RFC 2/5] cfg80211: make cfg80211_leave_all() available outside of sysfs Luis R. Rodriguez
2013-11-13 18:12 ` [RFC 3/5] cfg80211: add regulatory quiescing support Luis R. Rodriguez
2013-11-13 21:22   ` Johannes Berg
2013-11-14 14:11     ` Luis R. Rodriguez
2013-11-14 14:44       ` Johannes Berg
2013-11-14 15:18         ` Luis R. Rodriguez
2013-11-25 15:59           ` Johannes Berg
2014-01-24 23:35             ` Luis R. Rodriguez
2014-01-24 23:37               ` Johannes Berg
2013-11-25 15:59           ` Johannes Berg
2013-11-13 18:12 ` [RFC 4/5] cfg80211: add DFS region capability support Luis R. Rodriguez
2013-11-13 21:28   ` Johannes Berg
2013-11-14 14:31     ` Luis R. Rodriguez
2013-11-14 14:48       ` Johannes Berg
2013-11-14 15:33         ` Luis R. Rodriguez
2013-11-14 15:29           ` Johannes Berg
2013-11-14 15:34             ` Luis R. Rodriguez
2013-11-14 16:13               ` Simon Wunderlich
2013-11-15 12:05                 ` Luis R. Rodriguez
2013-11-13 18:12 ` [RFC 5/5] cfg80211: DFS check dfs_region before usage Luis R. Rodriguez
2013-11-13 21:29   ` Johannes Berg
2013-11-14 10:15     ` Janusz Dziedzic
2013-11-14 11:52       ` Janusz Dziedzic
2013-11-14 14:46         ` Luis R. Rodriguez
2013-11-15  9:37           ` Janusz Dziedzic
2013-11-15 12:01             ` Luis R. Rodriguez
2013-11-14 14:35       ` Luis R. Rodriguez
2013-11-14 14:33     ` Luis R. Rodriguez
2013-11-13 18:48 ` [RFC 0/5] cfg80211: regulatory quiescing and exporting DFS regions Johannes Berg
2013-11-13 18:57   ` Luis R. Rodriguez
2013-11-13 19:12     ` Johannes Berg
2013-11-13 19:13     ` Johannes Berg
2013-11-14 14:49       ` Luis R. Rodriguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1384366379-25301-1-git-send-email-mcgrof@do-not-panic.com \
    --to=mcgrof@do-not-panic.com \
    --cc=j@w1.fi \
    --cc=janusz.dziedzic@tieto.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rsunki@qca.qualcomm.com \
    --cc=sunitb@qca.qualcomm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).