All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Luka Gejak <luka.gejak@linux.dev>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Michael Straube" <straube.linux@gmail.com>,
	Peter Robinson <pbrobinson@gmail.com>,
	Bitterblue Smith <rtl8821cerfe2@gmail.com>
Subject: RE: [PATCH v2 01/11] wifi: rtw88: add the RTL8723B chip type and SDIO helper
Date: Mon, 3 Aug 2026 02:54:34 +0000	[thread overview]
Message-ID: <73128dc41c964b9eaeae0ae9a108f5b6@realtek.com> (raw)
In-Reply-To: <2AE57F1B-84FE-4BC6-A0E1-D8B61A90F3F0@linux.dev>

Luka Gejak <luka.gejak@linux.dev> wrote:
> On July 31, 2026 3:29:40 AM GMT+02:00, Ping-Ke Shih <pkshih@realtek.com> wrote:
> > Should receive filter implement in rtw_ops_configure_filter()?
> 
> Moot now, the receive filter handling goes with the patch I am
> dropping. For the record you were pointing at something real, although
> not quite where I first placed it.
> 
> rtw8723b.c does seed hal.rcr in mac_init, so it is not the problem. The
> asymmetry is in rtw_ops_configure_filter() itself: entering promiscuous
> clears BIT_CBSSID_BCN and BIT_CBSSID_DATA together, but leaving it
> restores only BIT_CBSSID_BCN. CBSSID_DATA is therefore gone from
> hal.rcr for good after the first scan, on any chip, until the next
> mac_init. That is what the per-association forcing was compensating
> for.
> 
> There is a second one next to it: rtw8723x.c writes WLAN_RCR_CFG
> straight to REG_RCR in mac_init without putting it into hal.rcr, so on
> 8723D and 8703B the first configure_filter() call replaces it with the
> core default from rtw_core_init(), which carries neither CBSSID bit nor
> AMF.
> 
> Both look worth fixing on their own and I am happy to send that
> separately if you agree with the reading. It is unrelated to this
> series.

I'm not sure if these specific things are hardly necessary. As you have
dropped many unnecessary patches copied from vendor driver, I think
you can consider if these can be dropped or integrate to existing 
chip_ops. I mean if you see somewhere you add rtw_is_8723bs(), just ask
yourself that is it actually necessary? Why don't existing chips need it?

> Happy to try that. Dropping the chip test would make the zero length
> check apply to every chip, so I would rather measure it on the 8703B
> path than assume; I do not have that hardware. If you are comfortable
> with it on inspection I will send it as a separate patch that removes
> the test entirely rather than fold it in here.

I don't have all hardware, so it is hard to me to verify the zero length
check. Even though I have hardware, it might happen rarely. So, maybe just
keep it as was... 

Ping-Ke


  reply	other threads:[~2026-08-03  2:54 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-25 15:04 [PATCH v2 00/11] wifi: rtw88: preparations for RTL8723B/RTL8723BS luka.gejak
2026-07-25 15:04 ` [PATCH v2 01/11] wifi: rtw88: add the RTL8723B chip type and SDIO helper luka.gejak
2026-07-27  7:12   ` Ping-Ke Shih
2026-07-27 13:25     ` Luka Gejak
2026-07-30  6:27       ` Luka Gejak
2026-07-30  9:21         ` Ping-Ke Shih
2026-07-30  7:44     ` luka.gejak
2026-07-30  9:17       ` Ping-Ke Shih
2026-07-30 14:28         ` Luka Gejak
2026-07-31  1:29           ` Ping-Ke Shih
2026-07-31  9:31             ` Luka Gejak
2026-08-03  2:54               ` Ping-Ke Shih [this message]
2026-07-25 15:04 ` [PATCH v2 02/11] wifi: rtw88: rx: mark zero length packets on RTL8723BS luka.gejak
2026-07-27  7:14   ` Ping-Ke Shih
2026-07-30  7:44     ` luka.gejak
2026-07-25 15:04 ` [PATCH v2 03/11] wifi: rtw88: fw: add the GNT_BT firmware command luka.gejak
2026-07-25 15:04 ` [PATCH v2 04/11] wifi: rtw88: fw: fix the reserved page upload on RTL8723BS luka.gejak
2026-07-27  7:37   ` Ping-Ke Shih
2026-07-30  7:44     ` luka.gejak
2026-07-25 15:04 ` [PATCH v2 05/11] wifi: rtw88: coex: add the RTL8723BS scan antenna workaround luka.gejak
2026-07-27  7:58   ` Ping-Ke Shih
2026-07-30  7:44     ` luka.gejak
2026-07-25 15:04 ` [PATCH v2 06/11] wifi: rtw88: coex: reassert the antenna path when associating luka.gejak
2026-07-27  8:21   ` Ping-Ke Shih
2026-07-30  7:44     ` luka.gejak
2026-07-25 15:04 ` [PATCH v2 07/11] wifi: rtw88: sdio: track free TX pages and OQT credits for RTL8723BS luka.gejak
2026-07-27  8:52   ` Ping-Ke Shih
2026-07-30  7:45     ` luka.gejak
2026-07-25 15:04 ` [PATCH v2 08/11] wifi: rtw88: sdio: set up RX aggregation and interrupts " luka.gejak
2026-07-27  8:59   ` Ping-Ke Shih
2026-07-30  7:45     ` luka.gejak
2026-07-25 15:04 ` [PATCH v2 09/11] wifi: rtw88: sdio: add TX back-pressure and retry on page starvation luka.gejak
2026-07-27  9:21   ` Ping-Ke Shih
2026-07-30  7:45     ` luka.gejak
2026-07-30  9:02       ` Ping-Ke Shih
2026-07-25 15:04 ` [PATCH v2 10/11] wifi: rtw88: record beacons from the target BSSID before authenticating luka.gejak
2026-07-27  9:27   ` Ping-Ke Shih
2026-07-30  7:45     ` luka.gejak
2026-07-25 15:04 ` [PATCH v2 11/11] wifi: rtw88: run the RTL8723BS association register sequence luka.gejak
2026-07-27  9:33   ` Ping-Ke Shih
2026-07-30  7:45     ` luka.gejak
2026-07-31  0:48       ` Ping-Ke Shih
2026-07-31  9:32         ` Luka Gejak
2026-08-03  3:13           ` 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=73128dc41c964b9eaeae0ae9a108f5b6@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luka.gejak@linux.dev \
    --cc=pbrobinson@gmail.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 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.