-
Notifications
You must be signed in to change notification settings - Fork 719
[nrf fromtree] net: wifi: Add support for regulatory domain configura… #1024
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
04bb1d1 to
d8ecdf7
Compare
d8ecdf7 to
01c7ad2
Compare
0bbafad to
01c7ad2
Compare
|
After multiple re-runs and debugging, the problem lies with So, this needs a fix. |
It's because we just started using this and all PRs so far had more than one commit I believe |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please change the gitlint commit message so it amends:
[nrf noup] ci: NCS-specific CI tweaks
2b663b1 to
01c7ad2
Compare
|
Depends on #1027 |
01c7ad2 to
1b0a1c9
Compare
f1be1ef to
5fe6fd6
Compare
…tion Wi-Fi bands are regulated by a governing body depending on operating country, add support for the user to provide a country of operation as a hint to the Wi-Fi chipset. Ideally if the chipset supports, this is all handled internally, in that case "get" is useful. But for testing and other use cases add a "set" as well, similar to "iw reg set" or "country_code=" configuration in hostapd/wpa_supplicant in Linux world. This add a new offload API operation "reg_domain" that can be used to either get or set the regulatory information. The validation is left to the underlying chipset, shell only does basic validation (XY/00). This is just a regulatory hint to the chipset, there could be other regulatory hints e.g., beacon that can override this configuration, so, an additional option to force this setting, despite other hints, is useful for testing purposes. FYI, the standard database used is [1]. [1] - https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/tree/db.txt Signed-off-by: Krishna T <[email protected]> (cherry picked from commit fadb1fd)
5fe6fd6 to
8bd40f1
Compare
…tion
Wi-Fi bands are regulated by a governing body depending on operating country, add support for the user to provide a country of operation as a hint to the Wi-Fi chipset.
Ideally if the chipset supports this is all handled internally, in that case "get" is useful but for testing and other usecases add a "set" as well, similar to "iw reg set" or "country_code=" configuration in hostapd/wpa_supplicant in Linux world.
This add a new offload API operation "reg_domain" that can be used to either get or set the regulatory information.
The validation is left to the underlying chipset, shell only does basic validation, (XY/00).
This is just a regulatory hint to the chipset, there could be other regulatory hints e.g., beacon that can override this configuration, so, an additional option to force this setting despite other hints is also given for testing purposes.
FYI, the standard database used is [1].
[1] - https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/tree/db.txt
Upstream PR: zephyrproject-rtos/zephyr#53541
Signed-off-by: Krishna T [email protected]