linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ilan Peer <ilan.peer@intel.com>
To: linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org, Ilan Peer <ilan.peer@intel.com>
Subject: [PATCH v3 5/6] cfg80211: Enable GO operation on indoor channels
Date: Mon, 27 Jan 2014 12:21:57 +0200	[thread overview]
Message-ID: <1390818118-27261-6-git-send-email-ilan.peer@intel.com> (raw)
In-Reply-To: <1390818118-27261-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 |    6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/net/wireless/chan.c b/net/wireless/chan.c
index 87a9d0e..4ae3cd0 100644
--- a/net/wireless/chan.c
+++ b/net/wireless/chan.c
@@ -611,14 +611,20 @@ 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)
 {
 	struct wireless_dev *wdev_iter;
+	struct wiphy *wiphy = wiphy_idx_to_wiphy(rdev->wiphy_idx);
 
 	ASSERT_RTNL();
 
+	if (regulatory_ir_allowed(wiphy, chan))
+		return true;
+
 	if (!(chan->flags & IEEE80211_CHAN_GO_CONCURRENT))
 		return false;
 
-- 
1.7.10.4


  parent reply	other threads:[~2014-01-27 10:20 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 10:21 [PATCH v3 0/6] Enable additional channels for use Ilan Peer
2014-01-27 10:21 ` [PATCH v3 1/6] cfg80211: Add indoor only and GO concurrent channel attributes Ilan Peer
2014-02-18 22:49   ` Luis R. Rodriguez
2014-02-19 14:44     ` Peer, Ilan
2014-01-27 10:21 ` [PATCH v3 2/6] cfg80211: Add Kconfig option for cellular BS hints Ilan Peer
2014-02-18 22:59   ` Luis R. Rodriguez
2014-01-27 10:21 ` [PATCH v3 3/6] cfg80211: Enable GO operation on additional channels Ilan Peer
2014-01-31 14:11   ` Johannes Berg
2014-02-02 19:20     ` Peer, Ilan
2014-02-03 12:46       ` Johannes Berg
2014-02-03 13:24         ` Peer, Ilan
2014-02-18 23:38   ` Luis R. Rodriguez
2014-02-19 14:52     ` Peer, Ilan
2014-02-19 15:47       ` Luis R. Rodriguez
2014-02-20  7:31         ` Peer, Ilan
2014-01-27 10:21 ` [PATCH v3 4/6] cfg80211: Add an option to hint indoor operation Ilan Peer
2014-01-31 14:13   ` Johannes Berg
2014-02-03 11:14   ` Ilan Peer
2014-02-19  0:07   ` Luis R. Rodriguez
2014-02-19 15:18     ` Peer, Ilan
2014-01-27 10:21 ` Ilan Peer [this message]
2014-02-19  0:10   ` [PATCH v3 5/6] cfg80211: Enable GO operation on indoor channels Luis R. Rodriguez
2014-01-27 10:21 ` [PATCH v3 6/6] mac80211: Enable initiating radiation " Ilan Peer
2014-02-19  0:15   ` Luis R. Rodriguez
2014-02-19 15:28     ` Peer, Ilan
2014-02-19 16:03       ` Luis R. Rodriguez
2014-02-20  7:58         ` Peer, Ilan
2014-02-21 23:31           ` Luis R. Rodriguez
2014-02-22 18:55             ` Peer, Ilan
2014-02-22 20:22               ` Luis R. Rodriguez
2014-02-23  7:23                 ` Peer, Ilan
2014-02-23  9:43                   ` Luis R. Rodriguez
2014-01-27 10:24 ` [PATCH v3 0/6] Enable additional channels for use Peer, Ilan
2014-02-09 16:06 ` Peer, Ilan
2014-02-18 22:17   ` Luis R. Rodriguez
2014-02-18 22:18     ` Luis R. Rodriguez
  -- strict thread matches above, loose matches on Subject: below --
2013-12-03 19:16 [PATCH v2 5/6] cfg80211: Enable GO operation on indoor channels Ilan Peer
2013-12-05 14:00 ` [PATCH v3 " 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=1390818118-27261-6-git-send-email-ilan.peer@intel.com \
    --to=ilan.peer@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wireless-regdb@lists.infradead.org \
    /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).