From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 8/8] wifi: rtw88: Extend rtw_debugfs_get_tx_pwr_tbl() for RTL8814AU
Date: Thu, 13 Feb 2025 18:13:06 +0200 [thread overview]
Message-ID: <14e4f32e-60d9-41a2-b1d9-beabbd106b01@gmail.com> (raw)
In-Reply-To: <b4001e93119b4f9cafa9b02dd328ff71@realtek.com>
On 13/02/2025 09:52, Ping-Ke Shih wrote:
> Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
>> Make it print the TX power details for RF paths C and D, and for 3SS and
>> 4SS rates.
>>
>> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
>> ---
>> drivers/net/wireless/realtek/rtw88/debug.c | 10 ++--------
>> 1 file changed, 2 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/net/wireless/realtek/rtw88/debug.c b/drivers/net/wireless/realtek/rtw88/debug.c
>> index 1adb03d1210a..0efb5c19b90e 100644
>> --- a/drivers/net/wireless/realtek/rtw88/debug.c
>> +++ b/drivers/net/wireless/realtek/rtw88/debug.c
>> @@ -708,20 +708,14 @@ static int rtw_debugfs_get_tx_pwr_tbl(struct seq_file *m, void *v)
>> "path", "rate", "pwr", "base", "byr", "lmt", "sar", "rem");
>>
>> mutex_lock(&hal->tx_power_mutex);
>> - for (path = RF_PATH_A; path <= RF_PATH_B; path++) {
>> + for (path = RF_PATH_A; path <= RF_PATH_D; path++) {
>
> Can we limit path and rate by efuse->hw_cap.nss or rf_path?
> Only showing two paths and 2SS rate for 2SS chips would avoid confusing.
>
Oh, right. That is a lot of unnecessary output with the 1SS and 2SS chips.
>> /* there is no CCK rates used in 5G */
>> if (hal->current_band_type == RTW_BAND_5G)
>> rate = DESC_RATE6M;
>> else
>> rate = DESC_RATE1M;
>>
>> - /* now, not support vht 3ss and vht 4ss*/
>> - for (; rate <= DESC_RATEVHT2SS_MCS9; rate++) {
>> - /* now, not support ht 3ss and ht 4ss*/
>> - if (rate > DESC_RATEMCS15 &&
>> - rate < DESC_RATEVHT1SS_MCS0)
>> - continue;
>> -
>> + for (; rate <= DESC_RATEVHT4SS_MCS9; rate++) {
>> rtw_get_tx_power_params(rtwdev, path, rate, bw,
>> ch, regd, &pwr_param);
>>
>> --
>> 2.48.1
>
prev parent reply other threads:[~2025-02-13 16:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 22:21 [PATCH 0/8] wifi: rtw88: Prepare to support RTL8814AU (part 2/2) Bitterblue Smith
2025-02-11 22:22 ` [PATCH 1/8] wifi: rtw88: Fix rtw_mac_power_switch() for RTL8814AU Bitterblue Smith
2025-02-13 7:29 ` Ping-Ke Shih
2025-02-11 22:22 ` [PATCH 2/8] wifi: rtw88: Fix rtw_desc_to_mcsrate() to handle MCS16-31 Bitterblue Smith
2025-02-13 7:30 ` Ping-Ke Shih
2025-02-13 16:12 ` Bitterblue Smith
2025-02-14 0:09 ` Ping-Ke Shih
2025-02-11 22:23 ` [PATCH 3/8] wifi: rtw88: Fix rtw_init_ht_cap() for RTL8814AU Bitterblue Smith
2025-02-13 7:35 ` Ping-Ke Shih
2025-02-11 22:23 ` [PATCH 4/8] wifi: rtw88: Fix rtw_init_vht_cap() " Bitterblue Smith
2025-02-13 7:39 ` Ping-Ke Shih
2025-02-11 22:24 ` [PATCH 5/8] wifi: rtw88: Fix rtw_rx_phy_stat() " Bitterblue Smith
2025-02-13 7:43 ` Ping-Ke Shih
2025-02-11 22:24 ` [PATCH 6/8] wifi: rtw88: Extend rtw_phy_config_swing_table() " Bitterblue Smith
2025-02-13 7:44 ` Ping-Ke Shih
2025-02-11 22:25 ` [PATCH 7/8] wifi: rtw88: Extend rtw_debugfs_get_phy_info() " Bitterblue Smith
2025-02-13 7:48 ` Ping-Ke Shih
2025-02-11 22:26 ` [PATCH 8/8] wifi: rtw88: Extend rtw_debugfs_get_tx_pwr_tbl() " Bitterblue Smith
2025-02-13 7:52 ` Ping-Ke Shih
2025-02-13 16:13 ` Bitterblue Smith [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=14e4f32e-60d9-41a2-b1d9-beabbd106b01@gmail.com \
--to=rtl8821cerfe2@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.