Home
last modified time | relevance | path

Searched full:regulatory (Results 1 – 25 of 117) sorted by relevance

12345

/linux/Documentation/networking/
H A Dregulatory.rst4 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 …]
H A Dindex.rst105 regulatory
/linux/include/net/
H A Dregulatory.h5 * 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/drivers/net/wireless/intel/iwlwifi/
H A Diwl-nvm-parse.h38 * struct iwl_reg_capa - struct for global regulatory capabilities, Used for
42 * for this regulatory domain.
44 * for this regulatory domain (valid only in 5 and 6 Ghz).
46 * for this regulatory domain (valid only in 5 and 6 Ghz).
48 * for this regulatory domain (valid only in 6 Ghz).
49 * @disable_11ax: 11ax is forbidden for this regulatory domain.
50 * @disable_11be: 11be is forbidden for this regulatory domain.
51 * @disable_11bn: UHR/11bn is not allowed for this regulatory domain
128 const __le16 *nvm_calib, const __le16 *regulatory,
135 * This function parses the regulatory channel data received as a
[all …]
H A Diwl-nvm-parse.c43 /* NVM REGULATORY -Section offset (in words) definitions */
60 /* NVM REGULATORY -Section offset (in words) definitions */
139 * enum iwl_reg_capa_flags_v1 - global flags applied for the whole regulatory
146 * for this regulatory domain (valid only in 5Ghz).
148 * for this regulatory domain (valid only in 5Ghz).
152 * for this regulatory domain (valid only in 5Ghz).
154 * @REG_CAPA_V1_11AX_DISABLED: 11ax is forbidden for this regulatory domain.
169 * enum iwl_reg_capa_flags_v2 - global flags applied for the whole regulatory
178 * for this regulatory domain (valid only in 5Ghz).
180 * for this regulatory domai
1516 iwl_parse_nvm_data(struct iwl_trans * trans,const struct iwl_rf_cfg * cfg,const struct iwl_fw * fw,const __be16 * nvm_hw,const __le16 * nvm_sw,const __le16 * nvm_calib,const __le16 * regulatory,const __le16 * mac_override,const __le16 * phy_sku,u8 tx_chains,u8 rx_chains) iwl_parse_nvm_data() argument
[all...]
/linux/net/wireless/
H A Dreg.c14 * DOC: Wireless regulatory infrastructure
17 * determine which regulatory domain it should be operating under, then
25 * In addition to all this we provide an extra layer of regulatory
26 * conformance. For drivers which do not have any regulatory
27 * information CRDA provides the complete regulatory solution.
59 * channels allowed by the current regulatory domain.
64 * enum reg_request_treatment - regulatory request treatment
66 * @REG_REQ_OK: continue processing the regulatory request
67 * @REG_REQ_IGNORE: ignore the regulatory request
68 * @REG_REQ_INTERSECT: the regulatory domai
[all...]
H A Dreg.h64 * guesses on regulatory to help with world roaming. This is only used for
67 * 1-11 are already enabled by the world regulatory domain; and on
79 * regulatory_hint_country_ie - hints a country IE as a regulatory domain
94 * in but for that they would have to use the regulatory extension
112 * This routine is a helper to restore regulatory settings to how they were
114 * beacon regulatory hints. The ieee80211_regdom module parameter will always
115 * be respected but if a user had set the regulatory domain that will take
171 * reg_reload_regdb - reload the regulatory.db firmware file
177 * reg_check_channels - schedule regulatory enforcement
/linux/drivers/net/wireless/intel/iwlwifi/fw/api/
H A Dnvm-reg.h11 * enum iwl_regulatory_and_nvm_subcmd_ids - regulatory/NVM commands
85 * @NVM_SECTION_TYPE_REGULATORY: regulatory section
88 * @NVM_SECTION_TYPE_REGULATORY_SDP: regulatory section used by 3168 series
175 * @NVM_MAC_SKU_FLAGS_REG_CHECK_ENABLED: true if regulatory checker enabled
216 * struct iwl_nvm_get_info_regulatory_v1 - regulatory information
218 * @channel_profile: regulatory data of this channel
228 * struct iwl_nvm_get_info_regulatory_v2 - regulatory information
231 * @channel_profile: regulatory data of this channel
244 * @regulatory: regulatory data
250 struct iwl_nvm_get_info_regulatory_v1 regulatory; member
[all …]
H A Ddhc.h96 * @max_reg_pwr_limit_ant_a: Antenna A regulatory power limits in dBm
97 * @max_reg_pwr_limit_ant_b: Antenna B regulatory power limits in dBm
/linux/Documentation/ABI/testing/
H A Dsysfs-driver-intc_sar7 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 Dregd.c29 * 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 */
365 * @reg: regulatory structure - used for country selection
366 * @initiator: the regulatory hint initiator
370 * regulatory SKUs.
375 * custom regulatory domai
[all...]
H A DKconfig41 bool "Atheros dynamic user regulatory hints"
50 bool "Atheros dynamic user regulatory testing"
/linux/drivers/net/wireless/realtek/rtw88/
H A Dregd.c23 __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 Dintel_sar.h53 * @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 D4965.h270 * 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 Dipw2100.rst40 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 Dipw2200.rst54 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/realtek/rtlwifi/rtl8192se/
H A Dfw.h74 /* 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 Drf.c176 /* 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/include/uapi/linux/
H A Dnl80211.h49 #define NL80211_MULTICAST_GROUP_REG "regulatory"
458 * regulatory domain. If %NL80211_ATTR_WIPHY is specified and the device
459 * has a private regulatory domain, it will be returned. Otherwise, the
461 * A device will have a private regulatory domain if it uses the
464 * the regulatory core to help with compliance. A dump version of this API
468 * its private regdomain is the only valid one for it. The regulatory
470 * @NL80211_CMD_SET_REG: Set current regulatory domain. CRDA sends this command
471 * after being queried by the kernel. CRDA replies by sending a regulatory
474 * NL80211_ATTR_REG_RULE_FLAGS, and a set of regulatory rules. Each
475 * regulatory rul
[all...]
/linux/Documentation/driver-api/80211/
H A Dcfg80211.rst143 Regulatory enforcement infrastructure
147 :doc: Regulatory enforcement infrastructure
/linux/drivers/net/wireless/quantenna/qtnfmac/
H A Dqlink.h67 * @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.
1538 * enum qlink_reg_rule_flags - regulatory rule flags
[all …]
/linux/drivers/net/wireless/intel/iwlwifi/mvm/
H A Dnvm.c236 const __le16 *sw, *calib, *regulatory, *mac_override, *phy_sku; in iwl_parse_nvm_sections()
254 /* SW and REGULATORY sections are mandatory */ in iwl_parse_nvm_sections()
285 regulatory = mvm->trans->cfg->nvm_type == IWL_NVM_SDP ?
296 regulatory, mac_override, phy_sku, in iwl_mvm_load_nvm_to_nic()
610 * Driver regulatory hint for initial update, this also informs the in iwl_mvm_init_mcc()
669 IWL_DEBUG_LAR(mvm, "RX: No change in the regulatory data\n"); in iwl_mvm_rx_chub_update_mcc()
221 const __le16 *sw, *calib, *regulatory, *mac_override, *phy_sku; iwl_parse_nvm_sections() local
/linux/drivers/net/wireless/broadcom/brcm80211/brcmsmac/
H A Dchannel.c20 #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()
711 /* Disable radio if all channels disallowed by regulatory */ in brcms_reg_notifier()
/linux/drivers/net/wireless/virtual/
H A Dmac80211_hwsim_main.c80 * enum hwsim_regtest - the type of regulatory tests we offer
82 * @HWSIM_REGTEST_DISABLED: No regulatory tests are performed,
84 * @HWSIM_REGTEST_DRIVER_REG_FOLLOW: Used for testing the driver regulatory
85 * hint, only one driver regulatory hint will be sent as such the
87 * @HWSIM_REGTEST_DRIVER_REG_ALL: Used for testing the driver regulatory
88 * request with all radios reporting the same regulatory domain.
90 * different regulatory domains requests. Expected behaviour is for
92 * respective regulatory requested domains. Subsequent radios will
95 * this by using a custom beacon-capable regulatory domain for the first
97 * @HWSIM_REGTEST_CUSTOM_WORLD: Used for testing the custom world regulatory
[all...]

12345