From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: <johannes@sipsolutions.net>, <johannes@sipsolutions.net>,
<linville@tuxdriver.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
<linux-wireless@vger.kernel.org>
Subject: [PATCH 03/12] cfg80211: export freq_reg_info()
Date: Thu, 22 Jan 2009 15:05:45 -0800 [thread overview]
Message-ID: <1232665554-26132-4-git-send-email-lrodriguez@atheros.com> (raw)
In-Reply-To: <1232665554-26132-3-git-send-email-lrodriguez@atheros.com>
This can be used by drivers on the reg_notifier()
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
---
include/net/wireless.h | 24 ++++++++++++++++++++++++
net/wireless/reg.c | 24 ++----------------------
2 files changed, 26 insertions(+), 22 deletions(-)
diff --git a/include/net/wireless.h b/include/net/wireless.h
index 585caad..a8971f6 100644
--- a/include/net/wireless.h
+++ b/include/net/wireless.h
@@ -418,4 +418,28 @@ extern void wiphy_apply_custom_regulatory(
struct wiphy *wiphy,
const struct ieee80211_regdomain *regd);
+/**
+ * freq_reg_info - get regulatory information for the given frequency
+ * @wiphy: the wiphy for which we want to process this rule for
+ * @center_freq: Frequency in KHz for which we want regulatory information for
+ * @bandwidth: the bandwidth requirement you have in KHz, if you do not have one
+ * you can set this to 0. If this frequency is allowed we then set
+ * this value to the maximum allowed bandwidth.
+ * @reg_rule: the regulatory rule which we have for this frequency
+ *
+ * Use this function to get the regulatory rule for a specific frequency on
+ * a given wireless device. If the device has a specific regulatory domain
+ * it wants to follow we respect that unless a country IE has been received
+ * and processed already.
+ *
+ * Returns 0 if it was able to find a valid regulatory rule which does
+ * apply to the given center_freq otherwise it returns non-zero. It will
+ * also return -ERANGE if we determine the given center_freq does not even have
+ * a regulatory rule for a frequency range in the center_freq's band. See
+ * freq_in_rule_band() for our current definition of a band -- this is purely
+ * subjective and right now its 802.11 specific.
+ */
+extern int freq_reg_info(struct wiphy *wiphy, u32 center_freq, u32 *bandwidth,
+ const struct ieee80211_reg_rule **reg_rule);
+
#endif /* __NET_WIRELESS_H */
diff --git a/net/wireless/reg.c b/net/wireless/reg.c
index 2f2f6f5..70691de 100644
--- a/net/wireless/reg.c
+++ b/net/wireless/reg.c
@@ -833,29 +833,9 @@ static int freq_reg_info_regd(struct wiphy *wiphy,
return !max_bandwidth;
}
+EXPORT_SYMBOL(freq_reg_info);
-/**
- * freq_reg_info - get regulatory information for the given frequency
- * @wiphy: the wiphy for which we want to process this rule for
- * @center_freq: Frequency in KHz for which we want regulatory information for
- * @bandwidth: the bandwidth requirement you have in KHz, if you do not have one
- * you can set this to 0. If this frequency is allowed we then set
- * this value to the maximum allowed bandwidth.
- * @reg_rule: the regulatory rule which we have for this frequency
- *
- * Use this function to get the regulatory rule for a specific frequency on
- * a given wireless device. If the device has a specific regulatory domain
- * it wants to follow we respect that unless a country IE has been received
- * and processed already.
- *
- * Returns 0 if it was able to find a valid regulatory rule which does
- * apply to the given center_freq otherwise it returns non-zero. It will
- * also return -ERANGE if we determine the given center_freq does not even have
- * a regulatory rule for a frequency range in the center_freq's band. See
- * freq_in_rule_band() for our current definition of a band -- this is purely
- * subjective and right now its 802.11 specific.
- */
-static int freq_reg_info(struct wiphy *wiphy, u32 center_freq, u32 *bandwidth,
+int freq_reg_info(struct wiphy *wiphy, u32 center_freq, u32 *bandwidth,
const struct ieee80211_reg_rule **reg_rule)
{
return freq_reg_info_regd(wiphy, center_freq,
--
1.6.1.rc3.51.g5832d
next prev parent reply other threads:[~2009-01-22 23:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 23:05 [PATCH 00/12] cfg80211/mac80211: few fixes/enhancements for regulatory Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 01/12] cfg80211: print correct intersected regulatory domain Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 02/12] cfg80211: add wiphy_apply_custom_regulatory() Luis R. Rodriguez
2009-01-22 23:05 ` Luis R. Rodriguez [this message]
2009-01-22 23:05 ` [PATCH 04/12] cfg80211: Fix sanity check on 5 GHz when processing country IE Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 05/12] cfg80211: process user requests only after previous user/driver/core requests Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 06/12] cfg80211: ignore consecutive equal regulatory hints Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 07/12] cfg80211: rename fw_handles_regulatory to custom_regulatory Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 08/12] cfg80211: move check for ignore_reg_update() on wiphy_update_regulatory() Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 09/12] cfg80211: pass more detailed regulatory request information on reg_notifier() Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 10/12] cfg80211: Allow for strict regulatory settings Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 11/12] mac80211: allow mac80211 drivers to get to struct ieee80211_hw from wiphy Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 12/12] cfg80211: allow users to help a driver's compliance Luis R. Rodriguez
2009-01-25 16:23 ` [PATCH 10/12] cfg80211: Allow for strict regulatory settings Johannes Berg
2009-01-25 16:24 ` [PATCH 00/12] cfg80211/mac80211: few fixes/enhancements for regulatory Johannes Berg
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=1232665554-26132-4-git-send-email-lrodriguez@atheros.com \
--to=lrodriguez@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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