From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"luka.gejak@linux.dev" <luka.gejak@linux.dev>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Michael Straube" <straube.linux@gmail.com>,
Peter Robinson <pbrobinson@gmail.com>,
Hans de Goede <johannes.goede@oss.qualcomm.com>
Subject: RE: [PATCH v4 4/7] wifi: rtw88: fw: handle the RTL8723BS management TX reports
Date: Fri, 14 Aug 2026 05:52:43 +0000 [thread overview]
Message-ID: <db559be3670b4d1691c0a225a283570b@realtek.com> (raw)
In-Reply-To: <4a6f14e0-1daa-4ac6-af10-988a38b14317@gmail.com>
Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> On 11/08/2026 12:12, luka.gejak@linux.dev wrote:
> > From: Luka Gejak <luka.gejak@linux.dev>
> >
> > The vendor firmware used by the RTL8723BS does not report management
> > frame transmission through C2H_CCX_TX_RPT. It uses event 0x12, and
> > reuses 0x32 for scan probe reports, which rtw88 otherwise treats as a
> > WLAN_RFON event and completes the LPS leave check with.
> >
> > Route both events to the existing TX report handler for this chip, and
> > defer 0x32 to the worker instead of consuming it in the interrupt path,
> > so the reports are decoded and the LPS handshake is left alone. The
> > payload layout is the same as C2H_CCX_TX_RPT, so no separate decode is
> > needed.
> >
> > Without this, testers on ARM SDIO boards see "failed to get tx report
> > from firmware" and "firmware failed to leave lps state" once power save
> > engages under load.
> >
>
> Please see your reply from July 30 regarding this subject:
>
> https://lore.kernel.org/linux-wireless/20260730060903.30187-2-luka.gejak@linux.dev/
For the record, this patch is planned to remove by v5. [1] [2].
[1] https://lore.kernel.org/linux-wireless/57719CE4-BEE4-4A1E-B760-DFFD04FF865C@linux.dev/
[2] https://lore.kernel.org/linux-wireless/20260813055657.13506-1-luka.gejak@linux.dev/
next prev parent reply other threads:[~2026-08-14 5:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 9:11 [PATCH v4 0/7] wifi: rtw88: preparations for RTL8723B/RTL8723BS luka.gejak
2026-08-11 9:11 ` [PATCH v4 1/7] wifi: rtw88: add the RTL8723B chip type and SDIO helper luka.gejak
2026-08-14 7:15 ` Ping-Ke Shih
2026-08-11 9:11 ` [PATCH v4 2/7] wifi: rtw88: rx: mark zero length packets on RTL8723BS luka.gejak
2026-08-14 5:44 ` Ping-Ke Shih
2026-08-11 9:11 ` [PATCH v4 3/7] wifi: rtw88: tx: extend the TX report purge timeout to RTL8723BS luka.gejak
2026-08-14 7:15 ` Ping-Ke Shih
2026-08-11 9:12 ` [PATCH v4 4/7] wifi: rtw88: fw: handle the RTL8723BS management TX reports luka.gejak
2026-08-11 11:42 ` Bitterblue Smith
2026-08-14 5:52 ` Ping-Ke Shih [this message]
2026-08-11 9:12 ` [PATCH v4 5/7] wifi: rtw88: sdio: track free TX pages and OQT credits for RTL8723BS luka.gejak
2026-08-14 6:32 ` Ping-Ke Shih
2026-08-11 9:12 ` [PATCH v4 6/7] wifi: rtw88: sdio: set up RX aggregation and interrupts " luka.gejak
2026-08-14 6:41 ` Ping-Ke Shih
2026-08-11 9:12 ` [PATCH v4 7/7] wifi: rtw88: sdio: add TX back-pressure and retry on page starvation luka.gejak
2026-08-14 7:14 ` 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=db559be3670b4d1691c0a225a283570b@realtek.com \
--to=pkshih@realtek.com \
--cc=johannes.goede@oss.qualcomm.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.