Lines Matching +full:core +full:- +full:domain

6  * Copyright 2008-2009	Luis R. Rodriguez <mcgrof@qca.qualcomm.com>
25  * enum environment_cap - Environment parsed from country IE
38  * struct regulatory_request - used to keep track of regulatory requests
43  *	can be used by the wireless core to deal with conflicts
49  *	regulatory domain. We have a few special codes:
50  *	00 - World regulatory domain
51  *	99 - built by driver but a specific alpha2 cannot be determined
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
62  * @intersect: indicates whether the wireless core should intersect
63  *	the requested regulatory domain with the presently set regulatory
64  *	domain.
67  *	currently regulatory domain set on cfg80211 is updated from
91  * enum ieee80211_regulatory_flags - device regulatory flags
94  *	has its own custom regulatory domain and cannot identify the
99  *	or the regulatory core will set it for the wiphy.
101  *	wiphy_apply_custom_regulatory() the wireless core will
105  *	has regulatory domain that it wishes to be considered as the
107  *	domain programmed further regulatory hints shall only be considered
111  *	device's regulatory domain no user specified regulatory hint which
113  *	the device's original regulatory domain will be trusted as the
116  *	ISO3166-alpha2 country code. wiphys that use regulatory_hint()
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.
128  *	derived from the regulatory domain. The regulatory domain used will be
129  *	based on the ISO3166-alpha2 from country IE provided through
132  * 	all country IE information processed by the regulatory core. This will
140  * @REGULATORY_IGNORE_STALE_KICKOFF: the regulatory core will _not_ make sure
151  * @REGULATORY_WIPHY_SELF_MANAGED: for devices that employ wiphy-specific
154  *	A self-managed wiphys only employs regulatory information obtained from
156  *	beacon-hints, country-code IEs and hints from other devices on the same
157  *	system. Conversely, a self-managed wiphy does not share its regulatory
159  *	devices, one or more of which are self-managed, there might be
162  *	with non-locally originated hints.
193  * struct ieee80211_wmm_ac - used to store per ac wmm regulatory limitation
199  *      2^n-1 in the range 1..32767]