From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Bitterblue Smith" <rtl8821cerfe2@gmail.com>,
"Ping-Ke Shih" <pkshih@realtek.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
"Michael Straube" <straube.linux@gmail.com>,
"Peter Robinson" <pbrobinson@gmail.com>,
luka.gejak@linux.dev
Subject: Re: [PATCH v5 rtw-next 2/7] wifi: rtw88: assign the RCR per chip in rtw_core_init
Date: Wed, 30 Sep 2026 21:49:47 +0000 [thread overview]
Message-ID: <dbebd1c7deff61626d9f5daaf32332b0ca11f457@linux.dev> (raw)
In-Reply-To: <0f32b66a-c5fe-407a-92ff-387c3fe39e64@gmail.com>
September 30, 2026 at 23:46, "Bitterblue Smith" <rtl8821cerfe2@gmail.com mailto:rtl8821cerfe2@gmail.com?to=%22Bitterblue%20Smith%22%20%3Crtl8821cerfe2%40gmail.com%3E > wrote:
>
> On 01/10/2026 00:29, Luka Gejak wrote:
>
> >
> > September 30, 2026 at 23:27, "Bitterblue Smith" <rtl8821cerfe2@gmail.com mailto:rtl8821cerfe2@gmail.com?to=%22Bitterblue%20Smith%22%20%3Crtl8821cerfe2%40gmail.com%3E > wrote:
> >
> >
> >
> > >
> > > On 30/09/2026 23:36, Luka Gejak wrote:
> > >
> > September 30, 2026 at 20:03, "Bitterblue Smith" <rtl8821cerfe2@gmail.com mailto:rtl8821cerfe2@gmail.com?to=%22Bitterblue%20Smith%22%20%3Crtl8821cerfe2%40gmail.com%3E > wrote:
> >
> >
> >
> > On 30/09/2026 12:15, Luka Gejak wrote:
> >
> > The receive control word is the same for every chip today. The generic
> > default is written in rtw_core_init(), so a chip that needs a different
> > value has to overwrite it afterwards, in its own init path, far away
> > from where the default is decided.
> >
> > I still don't understand why RTL8723B(S) would need a different value.
> >
> >
> > Because 0x700060ce is what the vendor driver leaves in REG_RCR for this
> > chip, and it is what rtw8723x_mac_init() already writes for it. I have
> > both from tracing this card: a register dump at the end of
> > rtl8723bs_hal_init prints RCR=0x700060ce, and the same dump in rtw88
> > matched it field for field.
> >
> > The default is a different filter. It sets BIT_PKTCTL_DLEN, which the
> > 8723B vendor HAL and rtlwifi's rtl8723be never set, and it clears
> > BIT_AMF, BIT_CBSSID_DATA and BIT_CBSSID_BCN, which the vendor value
> > sets. Four bits in total.
> >
> > >
> > > It will work fine...
> > >
> >
> > Want me to drop the patch?
> >
> Yes. If you check the vendor drivers for the other chips,
> they're all in the same situation.
>
Ok, I will drop it in v6.
> >
> > That value does not survive rtw_core_start(), which writes REG_RCR from
> > hal.rcr after power_on. The field is what keeps it. BIT_APP_FCS is the only
> > bit added on top, because rtw88 advertises RX_INCLUDES_FCS.
> >
> > Best regards,
> > Luka Gejak
> >
> > >
> > >
> > >
> >
>
next prev parent reply other threads:[~2026-09-30 21:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 9:15 [PATCH v5 rtw-next 0/7] wifi: rtw88: add RTL8723B/RTL8723BS support Luka Gejak
2026-09-30 9:15 ` [PATCH v5 rtw-next 1/7] wifi: rtw88: move the shared 88xxa init helpers into the core Luka Gejak
2026-09-30 18:04 ` Bitterblue Smith
2026-09-30 20:53 ` Luka Gejak
2026-09-30 9:15 ` [PATCH v5 rtw-next 2/7] wifi: rtw88: assign the RCR per chip in rtw_core_init Luka Gejak
2026-09-30 18:03 ` Bitterblue Smith
2026-09-30 20:36 ` Luka Gejak
2026-09-30 21:27 ` Bitterblue Smith
2026-09-30 21:29 ` Luka Gejak
2026-09-30 21:46 ` Bitterblue Smith
2026-09-30 21:49 ` Luka Gejak [this message]
2026-09-30 9:16 ` [PATCH v5 rtw-next 3/7] wifi: rtw88: 8723b: add the RTL8723B register definitions Luka Gejak
2026-09-30 9:16 ` [PATCH v5 rtw-next 4/7] wifi: rtw88: 8723b: add the RTL8723B BB, RF and AGC tables Luka Gejak
2026-09-30 9:16 ` [PATCH v5 rtw-next 5/7] wifi: rtw88: 8723b: add the RTL8723B chip driver Luka Gejak
2026-09-30 18:03 ` Bitterblue Smith
2026-09-30 21:14 ` Luka Gejak
2026-09-30 9:16 ` [PATCH v5 rtw-next 6/7] wifi: rtw88: 8723bs: add the RTL8723BS SDIO bind Luka Gejak
2026-09-30 9:16 ` [PATCH v5 rtw-next 7/7] wifi: rtw88: 8723bs: enable building the RTL8723BS driver 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=dbebd1c7deff61626d9f5daaf32332b0ca11f457@linux.dev \
--to=luka.gejak@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pbrobinson@gmail.com \
--cc=pkshih@realtek.com \
--cc=rtl8821cerfe2@gmail.com \
--cc=straube.linux@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
all inboxes | Powered by JetHome®