From: <yhchuang@realtek.com>
To: <kvalo@codeaurora.org>
Cc: <linux-wireless@vger.kernel.org>, <briannorris@chromium.org>,
<tehuang@realtek.com>
Subject: [PATCH v4 0/2] rtw88: update regulatory settings
Date: Wed, 11 Mar 2020 17:45:22 +0800 [thread overview]
Message-ID: <20200311094524.18884-1-yhchuang@realtek.com> (raw)
From: Yan-Hsuan Chuang <yhchuang@realtek.com>
This patchset applies regulatory rules for Realtek's chip set.
Some of the modules are programmed country-specific code in the efuse.
And for this kind of modules, driver doesn't want the regulatory to be
changed, so the driver tends to not listen to the regulatory hint that
is notified by the stack. Otherwise if the modules are not programmed
to a country-specific code, then the world-wide (WW) settings will be
adopted. If the regulatory is WW, the driver will apply the settings
notified by the stack.
If anyone wants to allow regulatory being set from user-space tools
(ex: iw reg set), a compile option flag RTW88_REGD_USER_REG_HINTS
should be set to allow regulatory hist from user.
Also add "Adaptivity" support for some special country codes, because
they have to stop TX immediately if there's any energy detected.
v2 -> v3
* split patch set for further discussion
v3 -> v4
* squash patch set, since nobody has different idea for it
* "rtw88: add regulatory process strategy for different chipset" and
"rtw88: support dynamic user regulatory setting" are squashed
* modify the commit log to better describe it
* add a new patch for adaptivity support "rtw88: add adaptivity
support for EU/JP regulatory"
Tzu-En Huang (2):
rtw88: add regulatory process strategy for different chipset
rtw88: add adaptivity support for EU/JP regulatory
drivers/net/wireless/realtek/rtw88/Kconfig | 10 +++
drivers/net/wireless/realtek/rtw88/debug.c | 33 ++++++++
drivers/net/wireless/realtek/rtw88/main.c | 7 +-
drivers/net/wireless/realtek/rtw88/main.h | 33 ++++++++
drivers/net/wireless/realtek/rtw88/phy.c | 60 ++++++++++++++
drivers/net/wireless/realtek/rtw88/phy.h | 2 +
drivers/net/wireless/realtek/rtw88/reg.h | 2 +
drivers/net/wireless/realtek/rtw88/regd.c | 83 ++++++++++++++++---
drivers/net/wireless/realtek/rtw88/regd.h | 2 +
drivers/net/wireless/realtek/rtw88/rtw8822b.c | 41 +++++++++
drivers/net/wireless/realtek/rtw88/rtw8822b.h | 6 ++
drivers/net/wireless/realtek/rtw88/rtw8822c.c | 45 ++++++++++
drivers/net/wireless/realtek/rtw88/rtw8822c.h | 2 +
13 files changed, 313 insertions(+), 13 deletions(-)
--
2.17.1
next reply other threads:[~2020-03-11 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 9:45 yhchuang [this message]
2020-03-11 9:45 ` [PATCH v4 1/2] rtw88: add regulatory process strategy for different chipset yhchuang
2020-03-11 9:45 ` [PATCH v4 2/2] rtw88: add adaptivity support for EU/JP regulatory yhchuang
2020-03-11 23:28 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200311094524.18884-1-yhchuang@realtek.com \
--to=yhchuang@realtek.com \
--cc=briannorris@chromium.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tehuang@realtek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).