From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <kevin_yang@realtek.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wifi: rtw89: support parameter tables by RFE type
Date: Fri, 14 Apr 2023 12:22:36 +0000 (UTC) [thread overview]
Message-ID: <168147495263.16522.11700992716819261769.kvalo@kernel.org> (raw)
In-Reply-To: <20230330080331.37155-1-pkshih@realtek.com>
Ping-Ke Shih <pkshih@realtek.com> wrote:
> From: Zong-Zhe Yang <kevin_yang@realtek.com>
>
> One chip can have different RFE (RF front end) types which we will judge
> at runtime. And, different RFE types may use different RF parameter tables.
> Though we didn't really meet this case previously, we are going to meet it
> on upcoming chip RTL8851B. So, this commit handles parameter tables for
> runtime RFE type.
>
> We now encapsulate rtw89_txpwr_rule_<2/5/6>ghz tables into rtw89_rfe_parms.
> Then, each chip defines its default parameter tables, and if needed, it can
> configure extra parameter tables by RFE type. Finally we determine runtime
> parameter tables by RFE type if one is configured. Otherwise, we use the
> default parameter tables.
>
> For now, we just move all settings under default parameter tables. We will
> configure parameter tables by RFE types in separate commits afterwards.
>
> Signed-off-by: Zong-Zhe Yang <kevin_yang@realtek.com>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
Patch applied to wireless-next.git, thanks.
5395482afabb wifi: rtw89: support parameter tables by RFE type
--
https://patchwork.kernel.org/project/linux-wireless/patch/20230330080331.37155-1-pkshih@realtek.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2023-04-14 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 8:03 [PATCH] wifi: rtw89: support parameter tables by RFE type Ping-Ke Shih
2023-04-14 12:22 ` Kalle Valo [this message]
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=168147495263.16522.11700992716819261769.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=kevin_yang@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@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).