From: Abdurrahman Karadag <abdurrahmankaradag19@gmail.com>
To: briannorris@chromium.org, kvalo@kernel.org
Cc: pkshih@realtek.com, linux-wireless@vger.kernel.org,
rtl8821cerfe2@gmail.com
Subject: Re: [PATCH rtw-next 0/2] rtw88: recover a stopped TX queue, and notice a stalled ring
Date: Sat, 3 Oct 2026 02:37:38 +0300 [thread overview]
Message-ID: <20261002233738.29618-1-abdurrahmankaradag19@gmail.com> (raw)
In-Reply-To: <20261002231013.11792-1-abdurrahmankaradag19@gmail.com>
Adding Brian Norris and Kalle Valo, who were missing from the
original Cc. The CI check is right: I generated the recipient list
with git history disabled, so the blamed authors were omitted.
The patches themselves are unchanged and are in the archive:
https://lore.kernel.org/linux-wireless/20261002231013.11792-1-abdurrahmankaradag19@gmail.com/
Patch 1 is the one that touches lines you wrote: for a queue stopped by
the PCI TX ring-full path, the stop reason is released only from the
completion loop in rtw_pci_tx_isr(). Resetting the rings drops the
descriptors whose completion would have carried that wake, so
ieee80211_restart_hw() cannot recover a device that had stopped a
queue. It comes with a reproducer and an A/B measurement.
Sorry for the extra mail.
next prev parent reply other threads:[~2026-10-02 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 23:10 [PATCH rtw-next 0/2] rtw88: recover a stopped TX queue, and notice a stalled ring Abdurrahman Karadag
2026-10-02 23:10 ` [PATCH rtw-next 1/2] wifi: rtw88: pci: wake the TX queues when the rings are reset Abdurrahman Karadag
2026-10-05 1:49 ` Ping-Ke Shih
2026-10-02 23:10 ` [PATCH rtw-next 2/2] wifi: rtw88: pci: warn when a TX ring stops advancing Abdurrahman Karadag
2026-10-05 1:52 ` Ping-Ke Shih
2026-10-02 23:37 ` Abdurrahman Karadag [this message]
2026-10-05 1:44 ` [PATCH rtw-next 0/2] rtw88: recover a stopped TX queue, and notice a stalled ring 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=20261002233738.29618-1-abdurrahmankaradag19@gmail.com \
--to=abdurrahmankaradag19@gmail.com \
--cc=briannorris@chromium.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=rtl8821cerfe2@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