| /openbmc/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 …]
|
| /openbmc/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 …]
|
| /openbmc/linux/net/wireless/ |
| H A D | Kconfig | 77 and willing to ensure your system will remain regulatory
80 for whatever reason regulatory compliance has not or
81 cannot yet be verified. Regulatory verification may at
87 regulatory certification on the system with the enabled
90 and approved environment by your local regulatory agency.
97 Require that in addition to the "regulatory.db" file a
98 "regulatory.db.p7s" can be loaded with a valid PKCS#7
99 signature for the regulatory.db file made by one of the
107 Allow the regulatory database to be signed by one of the keys for
111 This is currently only Seth Forshee's key, who is the regulatory
[all …]
|
| 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.
68 * channels allowed by the current regulatory domain.
73 * enum reg_request_treatment - regulatory request treatment
75 * @REG_REQ_OK: continue processing the regulatory request
76 * @REG_REQ_IGNORE: ignore the regulatory request
77 * @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
180 * reg_reload_regdb - reload the regulatory.db firmware file
|
| /openbmc/openbmc/poky/meta/recipes-kernel/wireless-regdb/ |
| H A D | wireless-regdb_2024.10.07.bb | 1 SUMMARY = "Wireless Central Regulatory Domain Database"
2 HOMEPAGE = "https://wireless.wiki.kernel.org/en/developers/regulatory/crda"
15 install -m 0644 regulatory.bin ${D}${nonarch_libdir}/crda/regulatory.bin
18 install -m 0644 -D regulatory.db ${D}${nonarch_base_libdir}/firmware/regulatory.db
19 install -m 0644 regulatory.db.p7s ${D}${nonarch_base_libdir}/firmware/regulatory.db.p7s
22 # Install static regulatory DB in /lib/firmware for kernel to load.
30 ${nonarch_base_libdir}/firmware/regulatory.db \
31 ${nonarch_base_libdir}/firmware/regulatory.db.p7s \
34 # Native users might want to use the source of regulatory DB.
|
| /openbmc/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
|
| /openbmc/linux/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| H A D | nvm-reg.h | 11 * enum iwl_regulatory_and_nvm_subcmd_ids - regulatory/NVM commands
77 * @NVM_SECTION_TYPE_REGULATORY: regulatory section
80 * @NVM_SECTION_TYPE_REGULATORY_SDP: regulatory section used by 3168 series
167 * @NVM_MAC_SKU_FLAGS_REG_CHECK_ENABLED: true if regulatory checker enabled
207 * struct iwl_nvm_get_info_regulatory - regulatory information
209 * @channel_profile: regulatory data of this channel
219 * struct iwl_nvm_get_info_regulatory - regulatory information
222 * @channel_profile: regulatory data of this channel
235 * @regulatory: regulatory data
241 struct iwl_nvm_get_info_regulatory_v1 regulatory; member
[all …]
|
| /openbmc/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"
|
| /openbmc/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
|
| H A D | iwl-nvm-parse.c | 45 /* NVM REGULATORY -Section offset (in words) definitions */
61 /* NVM REGULATORY -Section offset (in words) definitions */
176 * enum iwl_reg_capa_flags_v1 - global flags applied for the whole regulatory
183 * for this regulatory domain (valid only in 5Ghz).
185 * for this regulatory domain (valid only in 5Ghz).
189 * for this regulatory domain (valid only in 5Ghz).
191 * @REG_CAPA_V1_11AX_DISABLED: 11ax is forbidden for this regulatory domain.
206 * enum iwl_reg_capa_flags_v2 - global flags applied for the whole regulatory
215 * for this regulatory domain (valid only in 5Ghz).
217 * for this regulatory domain (valid only in 5Ghz).
[all …]
|
| /openbmc/linux/drivers/net/wireless/realtek/rtw89/ |
| H A D | regd.c | 402 struct rtw89_regulatory_info *regulatory = &rtwdev->regulatory; in rtw89_regd_init() local
407 regulatory->reg_6ghz_power = RTW89_REG_6GHZ_POWER_DFLT; in rtw89_regd_init()
414 rtwdev->regulatory.regd = chip_regd; in rtw89_regd_init()
420 rtwdev->regulatory.regd->alpha2); in rtw89_regd_init()
422 rtw89_warn(rtwdev, "failed to hint regulatory:%d\n", ret); in rtw89_regd_init()
428 rtw89_debug_regd(rtwdev, rtwdev->regulatory.regd, in rtw89_regd_init()
437 rtwdev->regulatory.regd = rtw89_regd_find_reg_by_name(request->alpha2); in rtw89_regd_notifier_apply()
439 * and it does not expect the regulatory will be modified by in rtw89_regd_notifier_apply()
443 !rtw89_regd_is_ww(rtwdev->regulatory.regd)) in rtw89_regd_notifier_apply()
463 rtw89_debug_regd(rtwdev, rtwdev->regulatory.regd, in rtw89_regd_notifier()
[all …]
|
| /openbmc/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 …]
|
| /openbmc/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
|
| /openbmc/openbmc/meta-openembedded/meta-networking/classes/ |
| H A D | kernel_wireless_regdb.bbclass | 2 # regulatory database if it was put under net/wireless/db.txt.
4 # This class copies the regulatory plaintext database to kernel sources before
|
| /openbmc/linux/drivers/net/wireless/ath/ath11k/ |
| H A D | reg.h | 11 #include <net/regulatory.h>
28 /* ATH11K Regulatory API's */
|
| /openbmc/linux/drivers/staging/rtl8712/ |
| H A D | rtl8712_hal.h | 69 unsigned char regulatory_class_0; /*regulatory class bit map 0*/
70 unsigned char regulatory_class_1; /*regulatory class bit map 1*/
71 unsigned char regulatory_class_2; /*regulatory class bit map 2*/
72 unsigned char regulatory_class_3; /*regulatory class bit map 3*/
|
| /openbmc/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 …]
|
| /openbmc/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
|
| /openbmc/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()
|
| /openbmc/openbmc/poky/meta/lib/oeqa/runtime/cases/ |
| H A D | parselogs-ignores-common.txt | 61 Direct firmware load for regulatory.db
62 failed to load regulatory.db
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | nl80211.h | 49 #define NL80211_MULTICAST_GROUP_REG "regulatory"
453 * regulatory domain. If %NL80211_ATTR_WIPHY is specified and the device
454 * has a private regulatory domain, it will be returned. Otherwise, the
456 * A device will have a private regulatory domain if it uses the
459 * the regulatory core to help with compliance. A dump version of this API
463 * its private regdomain is the only valid one for it. The regulatory
465 * @NL80211_CMD_SET_REG: Set current regulatory domain. CRDA sends this command
466 * after being queried by the kernel. CRDA replies by sending a regulatory
469 * NL80211_ATTR_REG_RULE_FLAGS, and a set of regulatory rules. Each
470 * regulatory rule is a nested set of attributes given by
[all …]
|
| /openbmc/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()
|