Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp372140ybh; Wed, 11 Mar 2020 02:45:49 -0700 (PDT) X-Google-Smtp-Source: ADFU+vu2K9vdj4+kiOdfjwcXhl5NE+z4q/yh2O4w9aNjWBdLxQG+ovBjNU+jZ+eoBHR6WQtRna0w X-Received: by 2002:a9d:b89:: with SMTP id 9mr1657167oth.297.1583919949446; Wed, 11 Mar 2020 02:45:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1583919949; cv=none; d=google.com; s=arc-20160816; b=hLxJGen6+xEITExNEuzVI08uJTfDx794cMfsAMJcfKq+7ebY9xEa2d6B5d7Ic2yPve EfTtqLkIU98cjGA38RiqmFGZFropfvQKljN/mONwmA51ZovrfSyvoLXEnkXJchtjJ/Y7 5VqCsOQlmFymNAJM7K+Hw9rMQaya+4rhzEGpcqKo8iBAPOdbUcwAYAIk8yzFgw5lYrtm OsI8ceMVYT/3K4B6bDLrBph4uQjdg6qa5VQxEMjj1d7tuhQsUutpYcj1odpIphLBWLsX 42guxOOxepE/Y4FvftE6D2lyr5zw79YDqZh2Jr0jreZZ+qN/8HY1yvATrQTjyjRkAURq fpsg== 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=iDJXvGL6bk3D1tWLHoXPZCvt0Jm9kQ05cj7fF/C9XoI=; b=YOSFrTulQTplVXacPzCM3mb0y2k7QGle5yjWx04FCZyfZBadtNgg53W5F5FKxXJM6C zhLyTLtynyxbwBoVsLMLF9OA0jLguGG2jkPZi7IUFm5odYWYQAP6DeKSKJ0aGtHLM3MT IYeHSALi+YuYCD7li9R4egYVeY3HSMLmAeP9BGr85gpaoRjCWT5NkAfQ5BtkPcWeY0yv 4nRZNLt2T/iEP3oRRclOLMJv75wZBy8RIYMtCf78GGBPyOks5hcJY2XexNl51AYa8+sM tQAOHtIazEWsrdCryc5/ze5h8+sRa7m6wM/YHrBJFxSp0+CPTGaUxnsVieMiCzjGjU3l YrfA== 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 d16si813719otp.135.2020.03.11.02.45.39; Wed, 11 Mar 2020 02:45:49 -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 S1728444AbgCKJpf (ORCPT + 99 others); Wed, 11 Mar 2020 05:45:35 -0400 Received: from rtits2.realtek.com ([211.75.126.72]:51075 "EHLO rtits2.realtek.com.tw" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728255AbgCKJpf (ORCPT ); Wed, 11 Mar 2020 05:45:35 -0400 Authenticated-By: X-SpamFilter-By: BOX Solutions SpamTrap 5.62 with qID 02B9jR7e019753, 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 02B9jR7e019753 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 11 Mar 2020 17:45:27 +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; Wed, 11 Mar 2020 17:45:26 +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; Wed, 11 Mar 2020 17:45:26 +0800 From: To: CC: , , Subject: [PATCH v4 0/2] rtw88: update regulatory settings Date: Wed, 11 Mar 2020 17:45:22 +0800 Message-ID: <20200311094524.18884-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" 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