Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Authenticated-By: 
From:   <yhchuang@realtek.com>
To:     <kvalo@codeaurora.org>
CC:     <linux-wireless@vger.kernel.org>, <tehuang@realtek.com>,
        <briannorris@chromium.org>
Subject: [PATCH v8 0/2] rtw88: update regulatory settings
Date:   Fri, 31 Jul 2020 10:46:05 +0800
Message-ID: <20200731024607.5817-1-yhchuang@realtek.com>
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

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"

v4 -> v5
  * check return value of kstrtobool()

v5 -> v6
  * remove custom world-wide, use stack world-wide
  * surface err codes by printing logs
  * fix incorrect debugfs set parameter for edcca enable

v6 -> v7
  * restore custom world-wide, because of not to modify USER settings
  * modify commit message to be more clear

v7 -> v8
  * rebase on top of master
  * check return value for kstrtobool()
  * fix debugfs dereference
  * accept the same country with driver notified from stack
  * some wording refine


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    | 37 +++++++
 drivers/net/wireless/realtek/rtw88/main.c     |  8 +-
 drivers/net/wireless/realtek/rtw88/main.h     | 32 +++++++
 drivers/net/wireless/realtek/rtw88/phy.c      | 61 ++++++++++++
 drivers/net/wireless/realtek/rtw88/phy.h      |  2 +
 drivers/net/wireless/realtek/rtw88/reg.h      |  2 +
 drivers/net/wireless/realtek/rtw88/regd.c     | 96 +++++++++++++++++--
 drivers/net/wireless/realtek/rtw88/regd.h     |  4 +
 drivers/net/wireless/realtek/rtw88/rtw8822b.c | 43 +++++++++
 drivers/net/wireless/realtek/rtw88/rtw8822b.h |  8 ++
 drivers/net/wireless/realtek/rtw88/rtw8822c.c | 47 +++++++++
 drivers/net/wireless/realtek/rtw88/rtw8822c.h |  3 +
 13 files changed, 341 insertions(+), 12 deletions(-)

-- 
2.17.1