Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Ping-Ke Shih" <pkshih@realtek.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH rtw-next] wifi: rtw88: 8723b: always report a single spatial stream
Date: Wed, 21 Oct 2026 04:18:53 +0000	[thread overview]
Message-ID: <8a1729fff0ea514f9e0acdecf08543c09374856d@linux.dev> (raw)
In-Reply-To: <c07aa592e1154c43a3def7c57fd8488e@realtek.com>

October 21, 2026 at 5:51 AM, "Ping-Ke Shih" <pkshih@realtek.com> wrote:


> 
> Luka Gejak <luka.gejak@linux.dev> wrote:
> 
> > 
> > RTL8723B only ever has one spatial stream. Set nss and ant_num to 1
> >  directly instead of deriving them from rf_path_num, which just happens
> >  to be 1 on this chip.
> >  
> >  Signed-off-by: Luka Gejak <luka.gejak@linux.dev>
> > 
> Acked-by: Ping-Ke Shih <pkshih@realtek.com>
> 
> > 
> > ---
> >  drivers/net/wireless/realtek/rtw88/rtw8723b.c | 9 +++------
> >  1 file changed, 3 insertions(+), 6 deletions(-)
> >  
> >  diff --git a/drivers/net/wireless/realtek/rtw88/rtw8723b.c
> >  b/drivers/net/wireless/realtek/rtw88/rtw8723b.c
> >  index 8bb9c03d769c..89190dd4f5c7 100644
> >  --- a/drivers/net/wireless/realtek/rtw88/rtw8723b.c
> >  +++ b/drivers/net/wireless/realtek/rtw88/rtw8723b.c
> >  @@ -2365,12 +2365,9 @@ static int rtw8723b_read_efuse(struct rtw_dev *rtwdev, u8 *log_map)
> >  if (efuse->power_track_type != 0)
> >  rtw_warn(rtwdev, "unsupported power track type\n");
> >  
> >  - /*
> >  - * No firmware hardware feature report exists, so fill the hardware
> >  - * capability here; a zero stream count kills the HT MCS set.
> >  - */
> >  - efuse->hw_cap.nss = max_t(u8, rtwdev->hal.rf_path_num, 1);
> >  - efuse->hw_cap.ant_num = efuse->hw_cap.nss;
> > 
> Curiously, is there real hardware encountered the problem?
> 

No, but Bitterblue pointed out it's unnecessary code.

> > 
> > + /* No firmware hardware feature report exists, so fill it in here. */
> >  + efuse->hw_cap.nss = 1;
> >  + efuse->hw_cap.ant_num = 1;
> >  efuse->hw_cap.bw = BIT(RTW_CHANNEL_WIDTH_20) |
> >  BIT(RTW_CHANNEL_WIDTH_40);
> >  
> >  --
> >  2.53.0
> >
>

      reply	other threads:[~2026-10-21  4:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 22:20 [PATCH rtw-next] wifi: rtw88: 8723b: always report a single spatial stream Luka Gejak
2026-10-21  3:51 ` Ping-Ke Shih
2026-10-21  4:18   ` Luka Gejak [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=8a1729fff0ea514f9e0acdecf08543c09374856d@linux.dev \
    --to=luka.gejak@linux.dev \
    --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