From: Kalle Valo <kvalo@codeaurora.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <tony0620emma@gmail.com>, <linux-wireless@vger.kernel.org>,
<timlee@realtek.com>, <kevin_yang@realtek.com>
Subject: Re: [PATCH v2 1/4] rtw88: upgrade rtw_regulatory mechanism and mapping
Date: Tue, 21 Sep 2021 14:52:15 +0000 (UTC) [thread overview]
Message-ID: <20210921145215.2E740C43460@smtp.codeaurora.org> (raw)
In-Reply-To: <20210830072014.12250-2-pkshih@realtek.com>
Ping-Ke Shih <pkshih@realtek.com> wrote:
> From: Zong-Zhe Yang <kevin_yang@realtek.com>
>
> Mapping table from country code to rtw_regulatory, which manages tx power
> limit according to countries, is updated. And mapping architecture is also
> upgraded. For more precise control on tx power limit, it allows different
> rtw_regulatory for different bands logically. Besides, a helper function
> to query rtw_regulatory for current band under current country is provided.
>
> For older chips, some newly added rtw_regulatory may not be configured.
> To avoid that those chips have no limit on some countries mapping to a
> newer rtw_regulatory after table update, a backward selection mechanism
> of rtw_regulatory is introduced. It can help chips use a rtw_regulatory
> which has been configured as an alternative of a newer one which is not
> configured.
>
> In addition, rtw88 actually doesn't manage channel plans by itself.
> Instead, it follows them from stack. So, correct some naming about
> chplan with regd, and remove the unnecessary channel control for now.
>
> Signed-off-by: Zong-Zhe Yang <kevin_yang@realtek.com>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
4 patches applied to wireless-drivers-next.git, thanks.
f8509c38ecec rtw88: upgrade rtw_regulatory mechanism and mapping
8d4fb3998c05 rtw88: add regulatory strategy by chip type
7285eb9693a2 rtw88: support adaptivity for ETSI/JP DFS region
fe7bc23a8c5e rtw88: move adaptivity mechanism to firmware
--
https://patchwork.kernel.org/project/linux-wireless/patch/20210830072014.12250-2-pkshih@realtek.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-09-21 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 7:20 [PATCH v2 0/4] rtw88: update regulartory mapping and adaptivity Ping-Ke Shih
2021-08-30 7:20 ` [PATCH v2 1/4] rtw88: upgrade rtw_regulatory mechanism and mapping Ping-Ke Shih
2021-09-21 14:52 ` Kalle Valo [this message]
2021-08-30 7:20 ` [PATCH v2 2/4] rtw88: add regulatory strategy by chip type Ping-Ke Shih
2021-08-30 7:20 ` [PATCH v2 3/4] rtw88: support adaptivity for ETSI/JP DFS region Ping-Ke Shih
2021-08-30 7:20 ` [PATCH v2 4/4] rtw88: move adaptivity mechanism to firmware Ping-Ke Shih
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=20210921145215.2E740C43460@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=kevin_yang@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=timlee@realtek.com \
--cc=tony0620emma@gmail.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).