From: Ilan Peer <ilan.peer@intel.com>
To: linux-wireless@vger.kernel.org
Cc: mcgrof@do-not-panic.com, Ilan Peer <ilan.peer@intel.com>
Subject: [PATCH v6 5/5] cfg80211: Enable GO operation on indoor channels
Date: Wed, 19 Feb 2014 17:39:37 +0200 [thread overview]
Message-ID: <1392824377-18254-6-git-send-email-ilan.peer@intel.com> (raw)
In-Reply-To: <1392824377-18254-1-git-send-email-ilan.peer@intel.com>
Allow GO operation on a channel marked with IEEE80211_CHAN_INDOOR_ONLY
iff there is a user hint indicating that the platform is operating in
an indoor environment, i.e., the platform is a printer or media center
device.
Signed-off-by: Ilan Peer <ilan.peer@intel.com>
---
net/wireless/chan.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/net/wireless/chan.c b/net/wireless/chan.c
index 1d8c990..b18367d 100644
--- a/net/wireless/chan.c
+++ b/net/wireless/chan.c
@@ -611,6 +611,8 @@ EXPORT_SYMBOL(cfg80211_chandef_usable);
* IEEE80211_CHAN_GO_CONCURRENT and there is an additional station interface
* associated to an AP on the same channel or on the same UNII band
* (assuming that the AP is an authorized master).
+ * In addition allow the GO to operate on a channel on which indoor operation is
+ * allowed, iff we are currently operating in an indoor environment.
*/
static bool cfg80211_go_permissive_chan(struct cfg80211_registered_device *rdev,
struct ieee80211_channel *chan)
@@ -621,8 +623,14 @@ static bool cfg80211_go_permissive_chan(struct cfg80211_registered_device *rdev,
ASSERT_RTNL();
if (!config_enabled(CONFIG_CFG80211_REG_RELAX_NO_IR) ||
- !(wiphy->regulatory_flags & REGULATORY_ENABLE_RELAX_NO_IR) ||
- !(chan->flags & IEEE80211_CHAN_GO_CONCURRENT))
+ !(wiphy->regulatory_flags & REGULATORY_ENABLE_RELAX_NO_IR))
+ return false;
+
+ if (regulatory_indoor_allowed() &&
+ (chan->flags & IEEE80211_CHAN_INDOOR_ONLY))
+ return true;
+
+ if (!(chan->flags & IEEE80211_CHAN_GO_CONCURRENT))
return false;
list_for_each_entry(wdev_iter, &rdev->wdev_list, list) {
--
1.7.10.4
next prev parent reply other threads:[~2014-02-19 15:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 15:39 [PATCH v4 0/5] Enable additional channels for use Ilan Peer
2014-02-19 15:39 ` [PATCH v4 1/5] cfg80211: Add indoor only and GO concurrent channel attributes Ilan Peer
2014-02-19 16:11 ` Luis R. Rodriguez
2014-02-19 17:36 ` Arend van Spriel
2014-02-19 17:56 ` Luis R. Rodriguez
2014-02-20 8:11 ` Peer, Ilan
2014-02-20 9:32 ` Peer, Ilan
2014-02-19 15:39 ` [PATCH v4 2/5] cfg80211: Add Kconfig option for cellular BS hints Ilan Peer
2014-02-19 15:39 ` [PATCH v4 3/5] cfg80211: Enable GO operation on additional channels Ilan Peer
2014-02-19 16:24 ` Luis R. Rodriguez
2014-02-20 11:08 ` Peer, Ilan
2014-02-19 15:39 ` [PATCH v4 4/5] cfg80211: Add an option to hint indoor operation Ilan Peer
2014-02-19 16:34 ` Luis R. Rodriguez
2014-02-19 15:39 ` Ilan Peer [this message]
2014-02-19 15:48 ` [PATCH v4 5/5] cfg80211: Enable GO operation on indoor channels Ilan Peer
2014-02-19 16:38 ` Luis R. Rodriguez
-- strict thread matches above, loose matches on Subject: below --
2014-02-23 7:12 [PATCH v6 0/5] Enable additional channels for use Ilan Peer
2014-02-23 7:13 ` [PATCH v6 5/5] cfg80211: Enable GO operation on indoor channels Ilan Peer
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=1392824377-18254-6-git-send-email-ilan.peer@intel.com \
--to=ilan.peer@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.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).