From: luka.gejak@linux.dev
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: Luka Gejak <luka.gejak@linux.dev>,
linux-wireless@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 11/11] wifi: rtw88: run the RTL8723BS association register sequence
Date: Thu, 30 Jul 2026 07:45:04 +0000 [thread overview]
Message-ID: <20260730074504.19725-10-luka.gejak@linux.dev> (raw)
In-Reply-To: <611b495996b74b278bfd769a9c045582@realtek.com>
From: Luka Gejak <luka.gejak@linux.dev>
On 27/07/2026 09:33, Ping-Ke Shih wrote:
>> + if (rtw_is_8723bs(rtwdev)) {
[...]
> I'm surprising that RTL8723BS needs so many special handing. Can you reduce
> them? At least, use rtw_chip_prepare_tx() to implement its specific
> functions.
Done. v3 adds a chip_ops::prepare_tx callback, and
rtw_ops_mgd_prepare_tx() is back to a single common path:
mutex_lock(&rtwdev->mutex);
rtw_leave_lps_deep(rtwdev);
rtw_coex_connect_notify(rtwdev, COEX_ASSOCIATE_START);
rtw_chip_prepare_tx(rtwdev, vif, info);
mutex_unlock(&rtwdev->mutex);
rtw_chip_prepare_tx() calls the chip callback when one is set and
otherwise keeps the existing deferred RF calibration, so no other chip
changes behaviour. The RTL8723BS callback does the IPS wake and the
join sequence, and the chip driver in the follow-up series points
.prepare_tx at it. That also removes the chip test from the helper
below it, per your comments on patch 05.
On reducing the rest: this patch is smaller in v3, but not as much as
I would like, and I want to be straight about why. Two things went:
- the beacon wait, once you made me measure it (see my reply on
patch 10), which took struct rtw_auth_sync with it
- two dead bool arguments, rtw8723bs_auth_rx_filter(accept_all) and
rtw_coex_8723bs_restore_pad_ctrl(keep_pta_owner), both of which had
a single value at every call site
What is left is the vendor start_clnt_join() register programming
itself: the BSSID-scoped receive filter, the response and basic rate
set from the BSS rate elements, preamble and slot time, TSF update, the
retry limit and the security config. I have removed these individually
on hardware and association fails or the AP drops us shortly after,
which is why they are still here rather than because I have not tried.
If the concern is that it sits in mac80211.c rather than a chip file, I
agree, and I would rather move the whole rtw8723bs_* block into
rtw8723b.c in the driver series than leave it in the common file. It is
in mac80211.c today only because this series lands before the chip
file exists. Tell me which you prefer and I will do it that way.
Best regards,
Luka Gejak
prev parent reply other threads:[~2026-07-30 7:45 UTC|newest]
Thread overview: 37+ 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-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 [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=20260730074504.19725-10-luka.gejak@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