linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 5/7] wifi: rtw88: Extend rtw_fw_send_ra_info() for RTL8814AU
Date: Mon, 27 Jan 2025 06:36:27 +0000	[thread overview]
Message-ID: <ca7380d8560046c4a2a2badde9302691@realtek.com> (raw)
In-Reply-To: <fa9ff2b4-6e1a-45e4-90de-db6fe0d4f433@gmail.com>

Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> The existing code is suitable for chips with up to 2 spatial streams.
> Inform the firmware about the rates it's allowed to use when
> transmitting 3 spatial streams.
> 
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> ---
>  drivers/net/wireless/realtek/rtw88/fw.c | 14 ++++++++++++++
>  drivers/net/wireless/realtek/rtw88/fw.h |  1 +
>  2 files changed, 15 insertions(+)
> 
> diff --git a/drivers/net/wireless/realtek/rtw88/fw.c b/drivers/net/wireless/realtek/rtw88/fw.c
> index 02389b7c6876..0ca1b139110d 100644
> --- a/drivers/net/wireless/realtek/rtw88/fw.c
> +++ b/drivers/net/wireless/realtek/rtw88/fw.c
> @@ -735,6 +735,7 @@ void rtw_fw_send_ra_info(struct rtw_dev *rtwdev, struct rtw_sta_info *si,
>  {
>         u8 h2c_pkt[H2C_PKT_SIZE] = {0};
>         bool disable_pt = true;
> +       u32 mask_hi;
> 
>         SET_H2C_CMD_ID_CLASS(h2c_pkt, H2C_CMD_RA_INFO);
> 
> @@ -755,6 +756,19 @@ void rtw_fw_send_ra_info(struct rtw_dev *rtwdev, struct rtw_sta_info *si,
>         si->init_ra_lv = 0;
> 
>         rtw_fw_send_h2c_command(rtwdev, h2c_pkt);
> +
> +       if (rtwdev->chip->rf_tbl[RF_PATH_C]) {

Using `efuse->hw_cap.nss >= 3` would be consistent with latter patch. 

> +               SET_H2C_CMD_ID_CLASS(h2c_pkt, H2C_CMD_RA_INFO_HI);
> +
> +               mask_hi = si->ra_mask >> 32;
> +
> +               SET_RA_INFO_RA_MASK0(h2c_pkt, (mask_hi & 0xff));
> +               SET_RA_INFO_RA_MASK1(h2c_pkt, (mask_hi & 0xff00) >> 8);
> +               SET_RA_INFO_RA_MASK2(h2c_pkt, (mask_hi & 0xff0000) >> 16);
> +               SET_RA_INFO_RA_MASK3(h2c_pkt, (mask_hi & 0xff000000) >> 24);
> +
> +               rtw_fw_send_h2c_command(rtwdev, h2c_pkt);
> +       }
>  }

Prefer calling RA_INFO LO/HI in the same level. I meant

rtw_fw_send_ra_info()
{
        rtw_fw_send_ra_info_lo(); // original RA info
    
        if (efuse->hw_cap.nss <= 2)
                return;

        rtw_fw_send_ra_info_hi();
}


  reply	other threads:[~2025-01-27  6:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-26 22:53 [PATCH 0/7] wifi: rtw88: Prepare to support RTL8814AU (part 1/2) Bitterblue Smith
2025-01-26 22:53 ` [PATCH 1/7] wifi: rtw88: Fix __rtw_download_firmware() for RTL8814AU Bitterblue Smith
2025-01-27  6:06   ` Ping-Ke Shih
2025-01-26 22:54 ` [PATCH 2/7] wifi: rtw88: Fix download_firmware_validate() " Bitterblue Smith
2025-01-27  6:21   ` Ping-Ke Shih
2025-01-26 22:55 ` [PATCH 3/7] wifi: rtw88: Extend struct rtw_pwr_track_tbl " Bitterblue Smith
2025-01-27  6:23   ` Ping-Ke Shih
2025-01-26 22:55 ` [PATCH 4/7] wifi: rtw88: Extend rf_base_addr and rf_sipi_addr " Bitterblue Smith
2025-01-27  6:26   ` Ping-Ke Shih
2025-01-26 22:56 ` [PATCH 5/7] wifi: rtw88: Extend rtw_fw_send_ra_info() " Bitterblue Smith
2025-01-27  6:36   ` Ping-Ke Shih [this message]
2025-01-27 23:18     ` Bitterblue Smith
2025-01-28  5:52       ` Ping-Ke Shih
2025-01-28 17:17         ` Bitterblue Smith
2025-01-29  2:43           ` Ping-Ke Shih
2025-01-29 23:14             ` Bitterblue Smith
2025-01-30  9:12               ` Ping-Ke Shih
2025-01-30 21:16                 ` Bitterblue Smith
2025-01-26 23:01 ` [PATCH 6/7] wifi: rtw88: Extend TX power stuff for 3-4 spatial streams Bitterblue Smith
2025-01-27  7:06   ` Ping-Ke Shih
2025-01-26 23:02 ` [PATCH 7/7] wifi: rtw88: Fix rtw_update_sta_info() for RTL8814AU Bitterblue Smith
2025-01-27  7:14   ` 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=ca7380d8560046c4a2a2badde9302691@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rtl8821cerfe2@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).