From: Luka Gejak <luka.gejak@linux.dev>
To: Ping-Ke Shih <pkshih@realtek.com>, linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Michael Straube <straube.linux@gmail.com>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>,
Peter Robinson <pbrobinson@gmail.com>,
Hans de Goede <johannes.goede@oss.qualcomm.com>,
luka.gejak@linux.dev
Subject: Re: [PATCH v3 0/5] wifi: rtw88: preparations for RTL8723B/RTL8723BS
Date: Tue, 11 Aug 2026 11:30:48 +0200 [thread overview]
Message-ID: <A850D677-5DD9-4626-9DAB-1C62F20E292F@linux.dev> (raw)
In-Reply-To: <20260804065425.17364-1-luka.gejak@linux.dev>
On August 4, 2026 8:54:20 AM GMT+02:00, luka.gejak@linux.dev wrote:
>From: Luka Gejak <luka.gejak@linux.dev>
>
>This is the first of two series adding support for the Realtek RTL8723B
>802.11n chipset and its RTL8723BS SDIO variant to rtw88. It contains
>only the changes to the shared rtw88 core that the chip driver depends
>on. The chip itself, the build glue and the MAINTAINERS entry are a
>second series.
>
>v1 had 19 patches, v2 had 11, this has 5.
>
...
Hi Ping-Ke,
I have sent a v4 that supersedes this series, before you review v3, so
you do not spend time on this one. As you suggested, I am noting it here
on the v3 cover.
v4 re-adds two patches that were dropped in v2, both on the TX report and
leave-LPS paths. Testing on slower ARM SDIO hosts, Peter Robinson on the
RFC and another tester on a Rockchip RK3288 board, reproduced "failed to
get tx report from firmware" and "firmware failed to leave lps state",
which my faster x86 host never hit. One of the two simply extends the
timeout from commit c80788f7c5ae ("wifi: rtw88: increase TX report
timeout to fix race condition"), which you already acked for the
RTL8723DU, to the RTL8723BS, since they hit the same off-channel-scan
race. The other routes the vendor firmware's management TX report
events so the LPS leave check is left alone.
Other patches from v3 remain unchanged.
v4:
https://lore.kernel.org/all/20260811091203.26841-1-luka.gejak@linux.dev/
Best regards,
Luka Gejak
prev parent reply other threads:[~2026-08-11 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 6:54 [PATCH v3 0/5] wifi: rtw88: preparations for RTL8723B/RTL8723BS luka.gejak
2026-08-04 6:54 ` [PATCH v3 1/5] wifi: rtw88: add the RTL8723B chip type and SDIO helper luka.gejak
2026-08-04 6:54 ` [PATCH v3 2/5] wifi: rtw88: rx: mark zero length packets on RTL8723BS luka.gejak
2026-08-04 6:54 ` [PATCH v3 3/5] wifi: rtw88: sdio: track free TX pages and OQT credits for RTL8723BS luka.gejak
2026-08-04 6:54 ` [PATCH v3 4/5] wifi: rtw88: sdio: set up RX aggregation and interrupts " luka.gejak
2026-08-04 6:54 ` [PATCH v3 5/5] wifi: rtw88: sdio: add TX back-pressure and retry on page starvation luka.gejak
2026-08-04 7:18 ` [PATCH v3 0/5] wifi: rtw88: preparations for RTL8723B/RTL8723BS Peter Robinson
2026-08-04 7:57 ` Luka Gejak
2026-08-11 9:30 ` 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=A850D677-5DD9-4626-9DAB-1C62F20E292F@linux.dev \
--to=luka.gejak@linux.dev \
--cc=johannes.goede@oss.qualcomm.com \
--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