Home
last modified time | relevance | path

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

123456

/linux-6.14.4/Documentation/networking/
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 …]
/linux-6.14.4/include/net/
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-6.14.4/net/wireless/
DKconfig74 and willing to ensure your system will remain regulatory
77 for whatever reason regulatory compliance has not or
78 cannot yet be verified. Regulatory verification may at
84 regulatory certification on the system with the enabled
87 and approved environment by your local regulatory agency.
94 Require that in addition to the "regulatory.db" file a
95 "regulatory.db.p7s" can be loaded with a valid PKCS#7
96 signature for the regulatory.db file made by one of the
104 Allow the regulatory database to be signed by one of the keys for
108 This is currently only Seth Forshee's key, who is the regulatory
[all …]
Dreg.c25 * 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 …]
Dreg.h75 * 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-6.14.4/drivers/net/wireless/realtek/rtw89/
Dregd.c347 struct rtw89_regulatory_info *regulatory = &rtwdev->regulatory; in rtw89_regd_setup_unii4() local
366 bitmap_fill(regulatory->block_unii4, RTW89_REGD_MAX_COUNTRY_NUM); in rtw89_regd_setup_unii4()
391 clear_bit(i, regulatory->block_unii4); in rtw89_regd_setup_unii4()
395 clear_bit(i, regulatory->block_unii4); in rtw89_regd_setup_unii4()
406 struct rtw89_regulatory_info *regulatory = &rtwdev->regulatory; in __rtw89_regd_setup_policy_6ghz() local
417 set_bit(index, regulatory->block_6ghz); in __rtw89_regd_setup_policy_6ghz()
419 clear_bit(index, regulatory->block_6ghz); in __rtw89_regd_setup_policy_6ghz()
424 struct rtw89_regulatory_info *regulatory = &rtwdev->regulatory; in rtw89_regd_setup_policy_6ghz() local
448 bitmap_fill(regulatory->block_6ghz, RTW89_REGD_MAX_COUNTRY_NUM); in rtw89_regd_setup_policy_6ghz()
476 struct rtw89_regulatory_info *regulatory = &rtwdev->regulatory; in rtw89_regd_setup_policy_6ghz_sp() local
[all …]
/linux-6.14.4/Documentation/ABI/testing/
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-6.14.4/drivers/net/wireless/ath/
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 */
363 * @reg: regulatory structure - used for country selection
364 * @initiator: the regulatory hint initiator
368 * regulatory SKUs.
373 * custom regulatory domain.
[all …]
DKconfig41 bool "Atheros dynamic user regulatory hints"
50 bool "Atheros dynamic user regulatory testing"
/linux-6.14.4/drivers/net/wireless/intel/iwlwifi/fw/api/
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
215 * struct iwl_nvm_get_info_regulatory_v1 - regulatory information
217 * @channel_profile: regulatory data of this channel
227 * struct iwl_nvm_get_info_regulatory - regulatory information
230 * @channel_profile: regulatory data of this channel
243 * @regulatory: regulatory data
249 struct iwl_nvm_get_info_regulatory_v1 regulatory; member
[all …]
/linux-6.14.4/drivers/net/wireless/intel/iwlwifi/
Diwl-nvm-parse.h36 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
Diwl-nvm-parse.c41 /* NVM REGULATORY -Section offset (in words) definitions */
58 /* NVM REGULATORY -Section offset (in words) definitions */
179 * enum iwl_reg_capa_flags_v1 - global flags applied for the whole regulatory
186 * for this regulatory domain (valid only in 5Ghz).
188 * for this regulatory domain (valid only in 5Ghz).
192 * for this regulatory domain (valid only in 5Ghz).
194 * @REG_CAPA_V1_11AX_DISABLED: 11ax is forbidden for this regulatory domain.
209 * enum iwl_reg_capa_flags_v2 - global flags applied for the whole regulatory
218 * for this regulatory domain (valid only in 5Ghz).
220 * for this regulatory domain (valid only in 5Ghz).
[all …]
/linux-6.14.4/drivers/net/wireless/realtek/rtw88/
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-6.14.4/drivers/platform/x86/intel/int1092/
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-6.14.4/drivers/net/wireless/intel/iwlegacy/
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-6.14.4/drivers/net/wireless/ath/ath11k/
Dreg.h11 #include <net/regulatory.h>
31 /* ATH11K Regulatory API's */
/linux-6.14.4/Documentation/networking/device_drivers/wifi/intel/
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
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-6.14.4/drivers/net/wireless/realtek/rtlwifi/rtl8192se/
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 */
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-6.14.4/include/uapi/linux/
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 rule is a nested set of attributes given by
[all …]
/linux-6.14.4/drivers/net/wireless/realtek/rtlwifi/
Dregd.c26 *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-6.14.4/Documentation/driver-api/80211/
Dcfg80211.rst143 Regulatory enforcement infrastructure
147 :doc: Regulatory enforcement infrastructure
/linux-6.14.4/drivers/net/wireless/intel/iwlwifi/mvm/
Dnvm.c221 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-6.14.4/drivers/net/wireless/quantenna/qtnfmac/
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.
1533 * enum qlink_reg_rule_flags - regulatory rule flags
[all …]

123456