Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp1254489ybh; Thu, 12 Mar 2020 20:49:53 -0700 (PDT) X-Google-Smtp-Source: ADFU+vu7GRogMfGQTtfnDV6+cP9mzAIt7gjF6rHYYHdqdwjCzU25RioMEjeWV/xTiA7vO23OLx+j X-Received: by 2002:aca:b7d5:: with SMTP id h204mr5197449oif.130.1584071393759; Thu, 12 Mar 2020 20:49:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584071393; cv=none; d=google.com; s=arc-20160816; b=d8AZznxfeXS3okrvIOY6kTzwlochug5SFu6s93Z+qUOzjs+QXWoRMSE8J6++5/JAII IlhphSbBZrd3abnlsCcnDk9GiPoxpGIUtrlxhGNPm3I+ru01WB0VeFQZ1bnl7Gx2jdl0 /TKjbltdTffR6yRnr7gOyYBK+bJYC9vYFB8EOkNHjNFPqu1+Fl/OWc5Wzy5RYpk1qu6K 2Ug9JKZ6Ceaxuq0zJdzitldoSj66eNwrpeKYjbGKcTEq+aSs5waoWJxnZsSReXmharhF 1pw486FhS2Q9Rr8J7fLXclAM6eIcz42DGfT9merOD0yztk/gOIAVxRmQkutZ5J9gDm9W 2wPw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:subject:cc :to:from:authenticated-by; bh=StSx0uRKmvEwFQYlJFEDv0QuZyq8SvMAfAyxR7/aeik=; b=B+owgdlcx7ZgKoODZxC1xmluUt/v9omLB8Jb+d4kxAW+HWejtTy4OUToT0M6NBiJHG gZ0zYjdU2/w2FmpqpTtOITESEDMHhNICLprFxR+2xTb3Cui/UvS5byYWlT3rlfgKUguj 3p90HJYBgAqC5Lw+ZiSxW0Tt/+Mwchy0o6uC4NPzili9jeOYhxldaVoW0euAb6hpMqBC XK5D4EMv7DtY9gQYvDyc1I9aZZGPeUkFjI1TPoTTV5z9KgUQoCLY++ZiuvehoOc6OV3P K4FyFuuovM4MdbU5+MfTIkqJHmx3TAteertLgm/rCe1UmUmkJdy+vTyfdBaq2RYKHxSU E6PQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i19si3456788oie.131.2020.03.12.20.49.37; Thu, 12 Mar 2020 20:49:53 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726393AbgCMDt2 (ORCPT + 99 others); Thu, 12 Mar 2020 23:49:28 -0400 Received: from rtits2.realtek.com ([211.75.126.72]:55849 "EHLO rtits2.realtek.com.tw" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726328AbgCMDt2 (ORCPT ); Thu, 12 Mar 2020 23:49:28 -0400 Authenticated-By: X-SpamFilter-By: BOX Solutions SpamTrap 5.62 with qID 02D3nKXF014829, This message is accepted by code: ctloc85258 Received: from mail.realtek.com (RTEXMB06.realtek.com.tw[172.21.6.99]) by rtits2.realtek.com.tw (8.15.2/2.57/5.78) with ESMTPS id 02D3nKXF014829 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 13 Mar 2020 11:49:20 +0800 Received: from RTEXMB04.realtek.com.tw (172.21.6.97) by RTEXMB06.realtek.com.tw (172.21.6.99) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1779.2; Fri, 13 Mar 2020 11:49:20 +0800 Received: from localhost.localdomain (172.21.68.128) by RTEXMB04.realtek.com.tw (172.21.6.97) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1779.2; Fri, 13 Mar 2020 11:49:20 +0800 From: To: CC: , , Subject: [PATCH v5 0/2] rtw88: update regulatory settings Date: Fri, 13 Mar 2020 11:49:16 +0800 Message-ID: <20200313034918.22222-1-yhchuang@realtek.com> X-Mailer: git-send-email 2.17.1 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [172.21.68.128] X-ClientProxiedBy: RTEXMB03.realtek.com.tw (172.21.6.96) To RTEXMB04.realtek.com.tw (172.21.6.97) Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org From: Yan-Hsuan Chuang 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() 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 | 39 +++++++++ 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, 319 insertions(+), 13 deletions(-) -- 2.17.1