summaryrefslogtreecommitdiff
path: root/net
diff options
context:
space:
mode:
authorJohannes Berg <johannes@sipsolutions.net>2008-10-21 09:42:38 +0200
committerJohn W. Linville <linville@tuxdriver.com>2008-10-31 19:00:41 -0400
commitcf03268e6ed6cfacaa5e32db41ea832c4d10438b (patch)
tree48820b35da3f48206682493f932212d6c46b2410 /net
parente37d4dffdffb7f834bd28d4ae8e3dcdf07fce508 (diff)
downloadlinux-3.10-cf03268e6ed6cfacaa5e32db41ea832c4d10438b.tar.gz
linux-3.10-cf03268e6ed6cfacaa5e32db41ea832c4d10438b.tar.bz2
linux-3.10-cf03268e6ed6cfacaa5e32db41ea832c4d10438b.zip
wireless: don't publish __regulatory_hint
This function requires an internal lock to be held, so it cannot be published to other modules in the kernel. Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net')
-rw-r--r--net/wireless/reg.h28
1 files changed, 28 insertions, 0 deletions
diff --git a/net/wireless/reg.h b/net/wireless/reg.h
index a33362872f3..a4845b140a8 100644
--- a/net/wireless/reg.h
+++ b/net/wireless/reg.h
@@ -10,4 +10,32 @@ void regulatory_exit(void);
int set_regdom(const struct ieee80211_regdomain *rd);
+/**
+ * __regulatory_hint - hint to the wireless core a regulatory domain
+ * @wiphy: if a driver is providing the hint this is the driver's very
+ * own &struct wiphy
+ * @alpha2: the ISO/IEC 3166 alpha2 being claimed the regulatory domain
+ * should be in. If @rd is set this should be NULL
+ * @rd: a complete regulatory domain, if passed the caller need not worry
+ * about freeing it
+ *
+ * The Wireless subsystem can use this function to hint to the wireless core
+ * what it believes should be the current regulatory domain by
+ * giving it an ISO/IEC 3166 alpha2 country code it knows its regulatory
+ * domain should be in or by providing a completely build regulatory domain.
+ *
+ * Returns -EALREADY if *a regulatory domain* has already been set. Note that
+ * this could be by another driver. It is safe for drivers to continue if
+ * -EALREADY is returned, if drivers are not capable of world roaming they
+ * should not register more channels than they support. Right now we only
+ * support listening to the first driver hint. If the driver is capable
+ * of world roaming but wants to respect its own EEPROM mappings for
+ * specific regulatory domains it should register the @reg_notifier callback
+ * on the &struct wiphy. Returns 0 if the hint went through fine or through an
+ * intersection operation. Otherwise a standard error code is returned.
+ *
+ */
+extern int __regulatory_hint(struct wiphy *wiphy, enum reg_set_by set_by,
+ const char *alpha2, struct ieee80211_regdomain *rd);
+
#endif /* __NET_WIRELESS_REG_H */