aboutsummaryrefslogtreecommitdiffstats
path: root/include/uapi/linux
diff options
context:
space:
mode:
Diffstat (limited to 'include/uapi/linux')
-rw-r--r--include/uapi/linux/nl80211.h10
1 files changed, 9 insertions, 1 deletions
diff --git a/include/uapi/linux/nl80211.h b/include/uapi/linux/nl80211.h
index b37bd5a1cb82..2d384d041224 100644
--- a/include/uapi/linux/nl80211.h
+++ b/include/uapi/linux/nl80211.h
@@ -252,7 +252,15 @@
252 * %NL80211_ATTR_IFINDEX. 252 * %NL80211_ATTR_IFINDEX.
253 * 253 *
254 * @NL80211_CMD_GET_REG: ask the wireless core to send us its currently set 254 * @NL80211_CMD_GET_REG: ask the wireless core to send us its currently set
255 * regulatory domain. 255 * regulatory domain. If %NL80211_ATTR_WIPHY is specified and the device
256 * has a private regulatory domain, it will be returned. Otherwise, the
257 * global regdomain will be returned.
258 * A device will have a private regulatory domain if it uses the
259 * regulatory_hint() API. Even when a private regdomain is used the channel
260 * information will still be mended according to further hints from
261 * the regulatory core to help with compliance. A dump version of this API
262 * is now available which will returns the global regdomain as well as
263 * all private regdomains of present wiphys (for those that have it).
256 * @NL80211_CMD_SET_REG: Set current regulatory domain. CRDA sends this command 264 * @NL80211_CMD_SET_REG: Set current regulatory domain. CRDA sends this command
257 * after being queried by the kernel. CRDA replies by sending a regulatory 265 * after being queried by the kernel. CRDA replies by sending a regulatory
258 * domain structure which consists of %NL80211_ATTR_REG_ALPHA set to our 266 * domain structure which consists of %NL80211_ATTR_REG_ALPHA set to our