From: Kalle Valo <kvalo@codeaurora.org>
To: Tony Chuang <yhchuang@realtek.com>
Cc: Chris Chiu <chiu@endlessm.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH v3 1/2] rtw88: add regulatory process strategy for different chipset
Date: Fri, 29 Nov 2019 05:23:28 +0000 [thread overview]
Message-ID: <0101016eb59d3246-c013abc9-4fbf-4825-9780-a85cff3f43d2-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <f93341159e4342479e646e49ec2ab8d2@realtek.com> (Tony Chuang's message of "Fri, 29 Nov 2019 02:29:41 +0000")
Tony Chuang <yhchuang@realtek.com> writes:
>> -----Original Message-----
>> From: Chris Chiu [mailto:chiu@endlessm.com]
>> Sent: Friday, October 25, 2019 11:54 AM
>> To: Tony Chuang
>> Cc: Kalle Valo; linux-wireless; Brian Norris
>> Subject: Re: [PATCH v3 1/2] rtw88: add regulatory process strategy for
>> different chipset
>>
>> On Tue, Oct 22, 2019 at 6:12 PM <yhchuang@realtek.com> wrote:
>> >
>> > From: Tzu-En Huang <tehuang@realtek.com>
>> >
>> > There are two kinds of country/regulatory efuse settings
>> > for Realtek's chipset, one is worldwide and the other is
>> > a specific country. For both settings, REGULATORY_STRICT_REG
>> > will be set, telling stack that devices original regulatory is
>> > the superset of any further settings.
>> >
>> > For the chipset with the country setting being a specific
>> > country, Realtek does not apply any new regulatory setting
>> > notifiers to the card.
>> >
>> > For the chipset with a worldwide regulatory setting,
>> > Realtek's custom worldwide regulatory setting will be
>> > provided via wiphy_apply_custom_regulatory().
>> > And if a new regulatory notification is set by
>> > NL80211_REGDOM_SET_BY_COUNTRY_IE, the new setting will be
>> > applied to the card.
>> >
>> > Signed-off-by: Tzu-En Huang <tehuang@realtek.com>
>> > Signed-off-by: Yan-Hsuan Chuang <yhchuang@realtek.com>
>> Reviewed-by: Chris Chiu <chiu@endlessm.com>
>>
>> Looks good to me.
>>
>> Chris
>
> Gentle ping of this patch set :)
This is on my queue. I just want to investigate this in detail and
haven't found enough free time to do that.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2019-11-29 5:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 10:12 [PATCH v3 0/2] rtw88: update regulatory settings yhchuang
2019-10-22 10:12 ` [PATCH v3 1/2] rtw88: add regulatory process strategy for different chipset yhchuang
2019-10-25 3:54 ` Chris Chiu
2019-11-29 2:29 ` Tony Chuang
2019-11-29 5:23 ` Kalle Valo [this message]
2020-02-12 8:47 ` Tony Chuang
2019-10-22 10:12 ` [PATCH v3 2/2] rtw88: support dynamic user regulatory setting yhchuang
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=0101016eb59d3246-c013abc9-4fbf-4825-9780-a85cff3f43d2-000000@us-west-2.amazonses.com \
--to=kvalo@codeaurora.org \
--cc=briannorris@chromium.org \
--cc=chiu@endlessm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=yhchuang@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).