Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Vincent Schurink <spam@acio.nl>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH rtw-next v2] wifi: rtw89: set RA init rate level from RSSI in RA update
Date: Fri, 13 Nov 2026 01:20:08 +0000	[thread overview]
Message-ID: <a913df5736a04e0eb0844ad4549ae241@realtek.com> (raw)
In-Reply-To: <20261112075622.32785-1-spam@acio.nl>

Vincent Schurink <spam@acio.nl> wrote:
> When a station associates to an AP, the AP does not know the RSSI of
> the station yet. Thus, rtw89_phy_ra_assoc() sends init_rate_lv 0 to the
> firmware. With this value, the firmware RA of RTL8922A uses 20 MHz and
> VHT-MCS 2 for the station. The firmware RA does not try a higher rate,
> also when the PER is 0. On an 80 MHz AP, the TCP throughput to the
> station stays at approximately 35 Mbit/s.

As rtw89_phy_ra_sta_update() does below periodically to update rate mask.

    ra_mask &= rtw89_phy_ra_mask_rssi(rtwdev, rssi, 0);

Could you try moving AP and station closer to see if this can improve?
(Please run over 1 minute to have enough time for the RA algorithm.)

> 
> Move the mapping from RSSI to init_rate_lv to a function, and use it in
> the RA association and in the RA update. The firmware uses
> init_rate_lv only together with upd_all. Thus, the RA update also sets
> upd_all one time, when the level changes from 0 to a known level.

The upd_all will reset RA context, so only do this once if RSSI is unknown
during association like your v1.

[...]

> @@ -509,6 +523,7 @@ void rtw89_phy_ra_update_sta_link(struct rtw89_dev *rtwdev,
>         struct rtw89_vif_link *rtwvif_link = rtwsta_link->rtwvif_link;
>         struct ieee80211_vif *vif = rtwvif_link_to_vif(rtwvif_link);
>         struct rtw89_ra_info *ra = &rtwsta_link->ra;
> +       u8 prev_lv = ra->init_rate_lv;
>         struct ieee80211_link_sta *link_sta;

reverse X'mas tree order.

> 
>         rcu_read_lock();
> @@ -519,6 +534,9 @@ void rtw89_phy_ra_update_sta_link(struct rtw89_dev *rtwdev,
> 
>         rcu_read_unlock();
> 
> +       ra->init_rate_lv = rtw89_phy_ra_get_init_rate_lv(rtwsta_link);
> +       if (!prev_lv && ra->init_rate_lv)
> +               ra->upd_all = 1;

As I mentioned above.

>         if (changed & IEEE80211_RC_SUPP_RATES_CHANGED)
>                 ra->upd_mask = 1;
>         if (changed & (IEEE80211_RC_BW_CHANGED | IEEE80211_RC_NSS_CHANGED))



      reply	other threads:[~2026-11-13  1:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12  7:56 [PATCH rtw-next v2] wifi: rtw89: set RA init rate level from RSSI in RA update Vincent Schurink
2026-11-13  1:20 ` Ping-Ke Shih [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=a913df5736a04e0eb0844ad4549ae241@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=spam@acio.nl \
    /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