From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Bitterblue Smith" <rtl8821cerfe2@gmail.com>,
linux-wireless@vger.kernel.org
Cc: "Ping-Ke Shih" <pkshih@realtek.com>
Subject: Re: [PATCH rtw-next v2 3/3] wifi: rtw88: 8723b: Read the chip variant from efuse
Date: Wed, 21 Oct 2026 04:42:26 +0000 [thread overview]
Message-ID: <90b2130ba51c61014706e96ad74d2ca1a0fb9e4c@linux.dev> (raw)
In-Reply-To: <a551ce83-278b-4844-98c5-95e0ada3596a@gmail.com>
October 20, 2026 at 10:53 PM, "Bitterblue Smith" <rtl8821cerfe2@gmail.com> wrote:
>
> The RTL8703AS appears to be a variant of RTL8723BS which doesn't support
> 40 MHz channel width, so read the chip variant from efuse and disable
> support for 40 MHz.
>
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> ---
> v2:
> - Split into a separate patch.
> - Get the byte from the efuse physical map stored in RAM instead of
> reading it again from the chip.
> - Use macros for the address, mask, and chip variants.
> ---
Reviewed-by: Luka Gejak <luka.gejak@linux.dev>
Tested-by: Luka Gejak <luka.gejak@linux.dev>
Best regards,
Luka Gejak
next prev parent reply other threads:[~2026-10-21 4:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 20:50 [PATCH rtw-next v2 1/3] wifi: rtw88: Pass the physical map to the read_efuse chip op Bitterblue Smith
2026-10-20 20:51 ` [PATCH rtw-next v2 2/3] wifi: rtw88: 8723b: Read the package type from efuse Bitterblue Smith
2026-10-21 3:42 ` Ping-Ke Shih
2026-10-21 4:41 ` Luka Gejak
2026-10-20 20:53 ` [PATCH rtw-next v2 3/3] wifi: rtw88: 8723b: Read the chip variant " Bitterblue Smith
2026-10-21 3:45 ` Ping-Ke Shih
2026-10-21 4:42 ` Luka Gejak [this message]
2026-10-21 3:39 ` [PATCH rtw-next v2 1/3] wifi: rtw88: Pass the physical map to the read_efuse chip op Ping-Ke Shih
2026-10-21 4:41 ` Luka Gejak
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=90b2130ba51c61014706e96ad74d2ca1a0fb9e4c@linux.dev \
--to=luka.gejak@linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--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 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.