| /linux/Documentation/networking/ |
| H A D | regulatory.rst | 4 Linux wireless regulatory documentation
8 regulatory infrastructure works.
12 https://wireless.wiki.kernel.org/en/developers/Regulatory
14 Keeping regulatory domains in userspace
17 Due to the dynamic nature of regulatory domains we keep them
19 to the kernel one regulatory domain to be used as the central
20 core regulatory domain all wireless devices should adhere to.
22 How to get regulatory domains to the kernel
25 When the regulatory domain is first set up, the kernel will request a
26 database file (regulatory.db) containing all the regulatory rules. It
[all …]
|
| /linux/include/net/ |
| H A D | regulatory.h | 5 * regulatory support structures
41 * struct regulatory_request - used to keep track of regulatory requests
52 * regulatory domain. We have a few special codes:
53 * 00 - World regulatory domain
55 * 98 - result of an intersection between two regulatory domains
56 * 97 - regulatory domain has not yet been configured
57 * @dfs_region: If CRDA responded with a regulatory domain that requires
66 * the requested regulatory domain with the presently set regulatory
70 * currently regulatory domain set on cfg80211 is updated from
71 * CRDA and can be used by other regulatory requests. When a
[all …]
|
| /linux/net/wireless/ |
| H A D | reg.c | 25 * DOC: Wireless regulatory infrastructure
28 * determine which regulatory domain it should be operating under, then
36 * In addition to all this we provide an extra layer of regulatory
37 * conformance. For drivers which do not have any regulatory
38 * information CRDA provides the complete regulatory solution.
70 * channels allowed by the current regulatory domain.
75 * enum reg_request_treatment - regulatory request treatment
77 * @REG_REQ_OK: continue processing the regulatory request
78 * @REG_REQ_IGNORE: ignore the regulatory request
79 * @REG_REQ_INTERSECT: the regulatory domain resulting from this request should
[all …]
|
| H A D | reg.h | 75 * guesses on regulatory to help with world roaming. This is only used for
78 * 1-11 are already enabled by the world regulatory domain; and on
90 * regulatory_hint_country_ie - hints a country IE as a regulatory domain
105 * in but for that they would have to use the regulatory extension
123 * This routine is a helper to restore regulatory settings to how they were
125 * beacon regulatory hints. The ieee80211_regdom module parameter will always
126 * be respected but if a user had set the regulatory domain that will take
182 * reg_reload_regdb - reload the regulatory.db firmware file
188 * reg_check_channels - schedule regulatory enforcement
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-intc_sar | 7 Specific Absorption Rate (SAR) regulatory mode is typically
11 the current SAR regulatory mode on the Dynamic SAR driver using
13 this sysfs node, the currently configured regulatory mode value
16 Acceptable regulatory modes are:
23 - The regulatory mode value has one of the above values.
24 - The default regulatory mode used in the driver is 0.
48 given host. The regulatory mode configured on Dynamic SAR
|
| /linux/drivers/net/wireless/ath/ |
| H A D | regd.c | 29 * This is a set of common rules used by our world regulatory domains.
30 * We have 12 world regulatory domains. To save space we consolidate
31 * the regulatory domains in 5 structures by frequency and change
35 /* Only these channels all allow active scan on all world regulatory domains */
38 /* We enable active scan on these a case by case basis by regulatory domain */
45 /* We allow IBSS on these on a case by case basis by regulatory domain */
363 * @reg: regulatory structure - used for country selection
364 * @initiator: the regulatory hint initiator
368 * regulatory SKUs.
373 * custom regulatory domain.
[all …]
|
| H A D | Kconfig | 41 bool "Atheros dynamic user regulatory hints"
50 bool "Atheros dynamic user regulatory testing"
|
| /linux/drivers/net/wireless/intel/iwlwifi/ |
| H A D | iwl-nvm-parse.h | 36 const __le16 *nvm_calib, const __le16 *regulatory,
43 * This function parses the regulatory channel data received as a
44 * MCC_UPDATE_CMD command. It returns a newly allocation regulatory domain,
45 * to be fed into the regulatory core. In case the geo_info is set handle
47 * If not given to the regulatory core, the user is responsible for freeing
|
| /linux/drivers/net/wireless/realtek/rtw88/ |
| H A D | regd.c | 23 __r->regulatory->alpha2[0], \
24 __r->regulatory->alpha2[1], \
25 __r->regulatory->txpwr_regd_2g, \
26 __r->regulatory->txpwr_regd_5g, \
352 * as the superset for our regulatory rule. in rtw_regd_init()
360 rtwdev->regd.regulatory = &rtw_reg_ww; in rtw_regd_init()
386 "failed to hint regulatory: %d\n", ret); in rtw_regd_hint()
403 !rtw_reg_is_ww(next_regd->regulatory)) { in rtw_regd_mgmt_worldwide()
416 rtw_reg_match(next_regd->regulatory, rtwdev->efuse.country_code)) { in rtw_regd_mgmt_programmed()
435 if (rtw_reg_is_ww(next_regd->regulatory)) { in rtw_regd_mgmt_setting()
[all …]
|
| /linux/drivers/platform/x86/intel/int1092/ |
| H A D | intel_sar.h | 53 * @reg_mode_needed: regulatory mode set by user for tests
69 * @reg_value: regulatory value
70 * Regulatory 0: FCC, 1: CE, 2: ISED
|
| /linux/drivers/net/wireless/intel/iwlegacy/ |
| H A D | 4965.h | 270 * 1) Regulatory information (max txpower and channel usage flags) is provided
307 * 1) Compare desired txpower vs. (EEPROM) regulatory limit for this channel.
308 * Do not exceed regulatory limit; reduce target txpower if necessary.
312 * regulatory limit by 3 dB (half-power) for each transmitter, so the
313 * combined total output of the 2 transmitters is within regulatory limits.
332 * no reduction (such as with regulatory txpower limits) is required.
363 * the middle set of measurements is closest to the regulatory limits,
454 * avoids any need to double-check for regulatory compliance after
482 * limit each transmitter to deliver a max of 3 dB below the regulatory limit
484 * txpower is within regulatory limits.
[all …]
|
| /linux/Documentation/networking/device_drivers/wifi/intel/ |
| H A D | ipw2100.rst | 40 governmental regulatory agency requirements for the regions that they
61 ensuring the regulatory compliance of the products, (ii) Intel will bear
64 the warranty and/or issues arising from regulatory non-compliance, and
68 Note: Many regulatory agencies consider Wireless LAN adapters to be
69 modules, and accordingly, condition system-level regulatory approval
75 part of a development project. Conformance to local regulatory
|
| H A D | ipw2200.rst | 54 governmental regulatory agency requirements for the regions that they
75 ensuring the regulatory compliance of the products, (ii) Intel will bear
78 the warranty and/or issues arising from regulatory non-compliance, and
82 Note: Many regulatory agencies consider Wireless LAN adapters to be
83 modules, and accordingly, condition system-level regulatory approval
89 part of a development project. Conformance to local regulatory
363 The geography code corresponds to a regulatory domain as shown in the
|
| /linux/drivers/net/wireless/ath/ath11k/ |
| H A D | reg.h | 11 #include <net/regulatory.h>
31 /* ATH11K Regulatory API's */
|
| /linux/drivers/net/wireless/realtek/rtlwifi/rtl8192se/ |
| H A D | fw.h | 74 /* regulatory class bit map 0 */
76 /* regulatory class bit map 1 */
78 /* regulatory class bit map 2 */
80 /* regulatory class bit map 3 */
|
| H A D | rf.c | 176 /* Realtek regulatory increase power diff defined in _rtl92s_get_txpower_writeval_byregulatory()
177 * by Realtek for regulatory */ in _rtl92s_get_txpower_writeval_byregulatory()
182 "Realtek regulatory, 40MHz, writeval = 0x%x\n", in _rtl92s_get_txpower_writeval_byregulatory()
203 "Realtek regulatory, 20MHz, writeval = 0x%x\n", in _rtl92s_get_txpower_writeval_byregulatory()
208 /* Better regulatory don't increase any power diff */ in _rtl92s_get_txpower_writeval_byregulatory()
211 "Better regulatory, writeval = 0x%x\n", writeval); in _rtl92s_get_txpower_writeval_byregulatory()
|
| /linux/drivers/net/wireless/realtek/rtlwifi/ |
| H A D | regd.c | 26 *scan on all world regulatory domains
33 *by case basis by regulatory domain
196 *on these channels. This is only done for specific regulatory SKUs in _rtl_reg_apply_active_scan_flags()
212 *custom regulatory domain. in _rtl_reg_apply_active_scan_flags()
|
| /linux/Documentation/driver-api/80211/ |
| H A D | cfg80211.rst | 143 Regulatory enforcement infrastructure
147 :doc: Regulatory enforcement infrastructure
|
| /linux/drivers/net/wireless/quantenna/qtnfmac/ |
| H A D | qlink.h | 67 * @QLINK_HW_CAPAB_REG_UPDATE: device can update it's regulatory region.
155 * @max_reg_power: maximum regulatory transmission power (in dBm)
158 * @beacon_found: helper to regulatory code to indicate when a beacon
279 * @QLINK_CMD_REG_NOTIFY: notify device about regulatory domain change. This
668 * enum qlink_user_reg_hint_type - type of user regulatory hint
690 * @info: variable portion of regulatory notifier callback.
1027 * enum qlink_dfs_regions - regulatory DFS regions
1055 * @n_reg_rules: number of regulatory rules TLVs in variable portion of the
1057 * @dfs_region: regulatory DFS region, one of &enum qlink_dfs_regions.
1533 * enum qlink_reg_rule_flags - regulatory rule flags
[all …]
|
| /linux/drivers/net/wireless/intel/iwlwifi/mvm/ |
| H A D | nvm.c | 221 const __le16 *sw, *calib, *regulatory, *mac_override, *phy_sku; in iwl_parse_nvm_sections() local
239 /* SW and REGULATORY sections are mandatory */ in iwl_parse_nvm_sections()
270 regulatory = mvm->trans->cfg->nvm_type == IWL_NVM_SDP ? in iwl_parse_nvm_sections()
281 regulatory, mac_override, phy_sku, in iwl_parse_nvm_sections()
580 * Driver regulatory hint for initial update, this also informs the in iwl_mvm_init_mcc()
639 IWL_DEBUG_LAR(mvm, "RX: No change in the regulatory data\n"); in iwl_mvm_rx_chub_update_mcc()
|
| /linux/drivers/staging/rtl8723bs/os_dep/ |
| H A D | wifi_regd.c | 18 * scan on all world regulatory domains
27 * by case basis by regulatory domain
|
| /linux/drivers/net/wireless/broadcom/brcm80211/brcmsmac/ |
| H A D | channel.c | 20 #include <net/regulatory.h>
304 * set the driver's current country and regulatory information
341 /* store the country code for passing up as a regulatory hint */ in brcms_c_channel_mgr_attach()
356 /* save default country for exiting 11d regulatory mode */ in brcms_c_channel_mgr_attach()
386 /* set or restore gmode as required by regulatory */ in brcms_c_channel_set_chanspec()
709 /* Disable radio if all channels disallowed by regulatory */ in brcms_reg_notifier()
|
| /linux/drivers/net/wireless/ath/ath9k/ |
| H A D | Kconfig | 92 Regulatory bodies around the world require that wireless device
106 have obtained appropriate regulatory body certification for a
|
| /linux/drivers/net/wireless/ath/ath12k/ |
| H A D | reg.c | 56 "Regulatory Notification received for %s\n", wiphy_name(wiphy)); in ath12k_reg_notifier()
65 ath12k_warn(ar->ab, "Unexpected Regulatory event for this wiphy\n"); in ath12k_reg_notifier()
245 * regulatory. in ath12k_regd_update()
630 * type and client type, after complete 6G regulatory support is added. in ath12k_reg_build_regd()
675 * for all 5G rules here. The regulatory core performs in ath12k_reg_build_regd()
|
| /linux/drivers/net/wireless/ath/carl9170/ |
| H A D | main.c | 1885 struct ath_regulatory *regulatory = &ar->common.regulatory; in carl9170_parse_eeprom() local
1931 regulatory->current_rd = le16_to_cpu(ar->eeprom.reg_domain[0]); in carl9170_parse_eeprom()
1945 ath_reg_notifier_apply(wiphy, request, &ar->common.regulatory); in carl9170_reg_notifier()
1950 struct ath_regulatory *regulatory = &ar->common.regulatory; in carl9170_register() local
1966 err = ath_regd_init(regulatory, ar->hw->wiphy, in carl9170_register()
1988 if (!ath_is_world_regd(regulatory)) in carl9170_register()
1989 regulatory_hint(ar->hw->wiphy, regulatory->alpha2); in carl9170_register()
|