From: Ping-Ke Shih <pkshih@realtek.com>
To: <kvalo@codeaurora.org>
Cc: <linux-wireless@vger.kernel.org>, <kevin_yang@realtek.com>
Subject: [PATCH v2 0/4] rtw89: update power limit and regulatory map tables
Date: Mon, 1 Nov 2021 17:31:02 +0800 [thread overview]
Message-ID: <20211101093106.28848-1-pkshih@realtek.com> (raw)
Update these two tables according to internal updates that follow the
latest regulations.
v2:
- First patch uses name instead of number to represent domain indices,
because second patch changes the indices according to internal tables.
With the name, the second patch has only small and clear changes.
- becomes 4 patches (v1 has 2 patches only)
1/2 of v1 is split into three patches, and 2/2 of v1 is equal to 4/4 of v2.
Zong-Zhe Yang (4):
rtw89: fill regd field of limit/limit_ru tables by enum
rtw89: update rtw89 regulation definition to R58-R31
rtw89: update tx power limit/limit_ru tables to R54
rtw89: update rtw89_regulatory map to R58-R31
drivers/net/wireless/realtek/rtw89/core.h | 9 +-
drivers/net/wireless/realtek/rtw89/phy.c | 12 +
drivers/net/wireless/realtek/rtw89/regd.c | 375 +-
.../wireless/realtek/rtw89/rtw8852a_table.c | 12201 +++++++++-------
4 files changed, 7177 insertions(+), 5420 deletions(-)
--
2.25.1
next reply other threads:[~2021-11-01 9:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 9:31 Ping-Ke Shih [this message]
2021-11-01 9:31 ` [PATCH v2 1/4] rtw89: fill regd field of limit/limit_ru tables by enum Ping-Ke Shih
2021-11-02 2:06 ` Brian Norris
2021-11-03 1:24 ` Pkshih
2021-11-26 16:10 ` Kalle Valo
2021-11-01 9:31 ` [PATCH v2 2/4] rtw89: update rtw89 regulation definition to R58-R31 Ping-Ke Shih
2021-11-01 9:31 ` [PATCH v2 3/4] rtw89: update tx power limit/limit_ru tables to R54 Ping-Ke Shih
2021-11-01 9:31 ` [PATCH v2 4/4] rtw89: update rtw89_regulatory map to R58-R31 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=20211101093106.28848-1-pkshih@realtek.com \
--to=pkshih@realtek.com \
--cc=kevin_yang@realtek.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
/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).