From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Alastair D'Silva" <alastair@d-silva.org>,
linux-wireless@vger.kernel.org,
"Ping-Ke Shih" <pkshih@realtek.com>,
"Kalle Valo" <kvalo@kernel.org>
Cc: "Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Ulf Hansson" <ulfh@kernel.org>,
linux-kernel@vger.kernel.org,
"Alastair D'Silva" <alastair@d-silva.org>
Subject: Re: [PATCH rtw-next v6 0/4] wifi: rtw88: sdio: Fix unhandled RX request interrupt storm
Date: Wed, 14 Oct 2026 09:12:07 +0000 [thread overview]
Message-ID: <cb1a2225374da5768bb138191a7d36c68d574e69@linux.dev> (raw)
In-Reply-To: <20261014074426.2183095-1-alastair@d-silva.org>
Hi Alastair,
October 14, 2026 at 9:44 AM, "Alastair D'Silva" <alastair@d-silva.org> wrote:
> On 3081-based SDIO chips (observed on RTL8821CS; RTL8822CS is inferred to
> be affected as it shares the 3081 architecture), hardware does not
> automatically clear the REG_SDIO_HISR_RX_REQUEST status bit when the RX
> FIFO becomes empty. Masking this bit out in software before writing back
> to HISR prevented it from ever being acknowledged in hardware, trapping
> the CPU core in an infinite interrupt storm that locked up the system upon
> receiving network traffic.
There are three 3081 parts with an SDIO front end, not two. 8822BS is
RTW_WCPU_3081 as well (rtw8822b.c:2527) and rtw8822bs.c is built as
rtw88_8822bs.o, so naming 8821CS and 8822CS only leaves it out. Patch 3
changes the interrupt path for all three at once and only the 8821CS was
probed, which is the one thing I would add to a series that Cc's stable.
If there is no run on 8822BS and 8822CS to hand, saying the same for both
would do, the way the cover already does for 8822CS.
Best regards,
Luka Gejak
prev parent reply other threads:[~2026-10-14 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 7:44 [PATCH rtw-next v6 0/4] wifi: rtw88: sdio: Fix unhandled RX request interrupt storm Alastair D'Silva
2026-10-14 7:44 ` [PATCH rtw-next v6 1/4] wifi: rtw88: sdio: Handle allocation and read errors in rtw_sdio_rxfifo_recv Alastair D'Silva
2026-10-14 7:44 ` [PATCH rtw-next v6 2/4] wifi: rtw88: sdio: Track running state and cancel TX worker on stop Alastair D'Silva
2026-10-14 9:12 ` Luka Gejak
2026-10-14 7:44 ` [PATCH rtw-next v6 3/4] wifi: rtw88: sdio: Fix unhandled RX request interrupt storm Alastair D'Silva
2026-10-14 9:13 ` Luka Gejak
2026-10-14 7:44 ` [PATCH rtw-next v6 4/4] wifi: rtw88: sdio: Split rtw_sdio_rx_isr into 8051 and 3081 variants Alastair D'Silva
2026-10-14 9:12 ` 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=cb1a2225374da5768bb138191a7d36c68d574e69@linux.dev \
--to=luka.gejak@linux.dev \
--cc=alastair@d-silva.org \
--cc=jernej.skrabec@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=pkshih@realtek.com \
--cc=ulfh@kernel.org \
/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.