Lines Matching full:regulatory

4  * regulatory support structures
38  * struct regulatory_request - used to keep track of regulatory requests
49  *	regulatory domain. We have a few special codes:
50  *	00 - World regulatory domain
52  *	98 - result of an intersection between two regulatory domains
53  *	97 - regulatory domain has not yet been configured
54  * @dfs_region: If CRDA responded with a regulatory domain that requires
63  *	the requested regulatory domain with the presently set regulatory
67  *	currently regulatory domain set on cfg80211 is updated from
68  *	CRDA and can be used by other regulatory requests. When a
91  * enum ieee80211_regulatory_flags - device regulatory flags
94  *	has its own custom regulatory domain and cannot identify the
96  *	we will disregard the first regulatory hint (when the
99  *	or the regulatory core will set it for the wiphy.
105  *	has regulatory domain that it wishes to be considered as the
106  *	superset for regulatory rules. After this device gets its regulatory
107  *	domain programmed further regulatory hints shall only be considered
108  *	for this device to enhance regulatory compliance, forcing the
109  *	device to only possibly use subsets of the original regulatory
111  *	device's regulatory domain no user specified regulatory hint which
113  *	the device's original regulatory domain will be trusted as the
114  *	base. You can program the superset of regulatory rules for this
117  *	will have their wiphy->regd programmed once the regulatory
118  *	domain is set, and all other regulatory hints will be ignored
119  *	until their own regulatory domain gets programmed.
122  *	cfg80211 due to regulatory beacon hints. For more information on beacon
128  *	derived from the regulatory domain. The regulatory domain used will be
132  * 	all country IE information processed by the regulatory core. This will
140  * @REGULATORY_IGNORE_STALE_KICKOFF: the regulatory core will _not_ make sure
154  *	A self-managed wiphys only employs regulatory information obtained from
157  *	system. Conversely, a self-managed wiphy does not share its regulatory
160  *	contradictory regulatory settings between them. Usage of flag is
193  * struct ieee80211_wmm_ac - used to store per ac wmm regulatory limitation