Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: <linville@tuxdriver.com>, <johannes@sipsolutions.net>,
	<linville@tuxdriver.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
	<linux-wireless@vger.kernel.org>
Subject: [PATCH 5/6] cfg80211: Add kdoc for struct regulatory_request
Date: Wed, 29 Oct 2008 18:19:53 -0700	[thread overview]
Message-ID: <1225329594-21704-6-git-send-email-lrodriguez@atheros.com> (raw)
In-Reply-To: <1225329594-21704-5-git-send-email-lrodriguez@atheros.com>

As regulatory_request gets bigger there will be more questions
of what things means, so clarify documenation for it and
keep track of the special alpha2 codes we use internally
and on the userspace regulatory agents.

Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
---
 net/wireless/reg.c |   22 +++++++++++++++++++---
 1 files changed, 19 insertions(+), 3 deletions(-)

diff --git a/net/wireless/reg.c b/net/wireless/reg.c
index be6667a..dd1020b 100644
--- a/net/wireless/reg.c
+++ b/net/wireless/reg.c
@@ -42,9 +42,24 @@
 #include "core.h"
 #include "reg.h"
 
-/*
- * wiphy is set if this request's initiator is
- * REGDOM_SET_BY_COUNTRY_IE or _DRIVER
+/**
+ * struct regulatory_request - receipt of last regulatory request
+ *
+ * @wiphy: this is set if this request's initiator is
+ * 	%REGDOM_SET_BY_COUNTRY_IE or %REGDOM_SET_BY_DRIVER. This
+ * 	can be used by the wireless core to deal with conflicts
+ * 	and potentially inform users of which devices specifically
+ * 	cased the conflicts.
+ * @initiator: indicates who sent this request, could be any of
+ * 	of those set in reg_set_by, %REGDOM_SET_BY_*
+ * @alpha2: the ISO / IEC 3166 alpha2 country code of the requested
+ * 	regulatory domain. We have a few special codes:
+ * 	00 - World regulatory domain
+ * 	99 - built by driver but a specific alpha2 cannot be determined
+ * 	98 - result of an intersection between two regulatory domains
+ * @intersect: indicates whether the wireless core should intersect
+ * 	the requested regulatory domain with the presently set regulatory
+ * 	domain.
  */
 struct regulatory_request {
 	struct wiphy *wiphy;
@@ -53,6 +68,7 @@ struct regulatory_request {
 	bool intersect;
 };
 
+/* Receipt of information from last regulatory request */
 static struct regulatory_request *last_request;
 
 /* To trigger userspace events */
-- 
1.5.6.3


  reply	other threads:[~2008-10-30  1:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  1:19 [PATCH 0/6] cfg80211: few regulatory updates Luis R. Rodriguez
2008-10-30  1:19 ` [PATCH 1/6] cfg80211: a reg rule is invalid if freq diff is 0 Luis R. Rodriguez
2008-10-30  1:19   ` [PATCH 2/6] cfg80211: Add regulatory domain intersection capability Luis R. Rodriguez
2008-10-30  1:19     ` [PATCH 3/6] cfg80211: make print_regdomain_info() static Luis R. Rodriguez
2008-10-30  1:19       ` [PATCH 4/6] cfg80211: make use of reg macros on REG_RULE Luis R. Rodriguez
2008-10-30  1:19         ` Luis R. Rodriguez [this message]
2008-10-30  1:19           ` [PATCH 6/6] cfg80211: enable 5 GHz band for world regulatory domain Luis R. Rodriguez
2008-10-30  9:24             ` Johannes Berg
2008-10-30 16:09               ` Luis R. Rodriguez
2008-10-30 17:18                 ` Johannes Berg
2008-10-30 17:43                   ` Luis R. Rodriguez
2008-10-30 18:12                   ` Jouni Malinen
2008-10-30  9:22   ` [PATCH 1/6] cfg80211: a reg rule is invalid if freq diff is 0 Johannes Berg
2008-10-30 19:40     ` 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=1225329594-21704-6-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