From: Ping-Ke Shih <pkshih@realtek.com>
To: Luka Gejak <luka.gejak@linux.dev>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>,
Kalle Valo <kvalo@kernel.org>
Cc: Yan-Hsuan Chuang <yhchuang@realtek.com>,
Brian Norris <briannorris@chromium.org>,
Stanislaw Gruszka <sgruszka@redhat.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw88: increase TX report timeout to fix race condition
Date: Wed, 6 May 2026 08:23:17 +0000 [thread overview]
Message-ID: <6fec8d91bf174dc99babbdf6d71767e5@realtek.com> (raw)
In-Reply-To: <39E7B292-F03C-4307-B0BE-62DEC191FED8@linux.dev>
> >> I also realize now that globally changing RTW_TX_PROBE_TIMEOUT to
> >> 2500ms is too heavy-handed. Since this impacts all rtw88 chips,
> >> including PCIe variants where 500ms might be exactly what is needed to
> >> catch a real firmware lockup, the blast radius is too large. How would
> >> you prefer I handle this for the v2 patch? I can either implement a
> >> more conservative global bump, or make the timeout dynamic based on
> >> the HCI interface so USB devices get a longer timeout to accommodate
> >> the bus latency during scans.
I'd limit this change to USB devices, even limit to RTL8723DU you tested.
As RTL8822CU supports hw_scan, the symptom might be different.
Ping-Ke
prev parent reply other threads:[~2026-05-06 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 15:04 [PATCH] wifi: rtw88: increase TX report timeout to fix race condition luka.gejak
2026-05-01 19:26 ` Bitterblue Smith
2026-05-01 20:46 ` Luka Gejak
2026-05-01 21:28 ` Bitterblue Smith
2026-05-01 21:33 ` Luka Gejak
2026-05-06 8:23 ` Ping-Ke Shih [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=6fec8d91bf174dc99babbdf6d71767e5@realtek.com \
--to=pkshih@realtek.com \
--cc=briannorris@chromium.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--cc=rtl8821cerfe2@gmail.com \
--cc=sgruszka@redhat.com \
--cc=stable@vger.kernel.org \
--cc=yhchuang@realtek.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