Linux wireless drivers development
 help / color / mirror / Atom feed
From: Mehmet Fide <mehmet.fide@gmail.com>
To: stable@vger.kernel.org
Cc: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	Ping-Ke Shih <pkshih@realtek.com>,
	linux-wireless@vger.kernel.org, mehmet.fide@screeningeagle.com
Subject: Please apply 13221be72034 ("wifi: rtw88: Handle C2H_ADAPTIVITY in rtw_fw_c2h_cmd_handle()") to 6.6.y and 6.12.y
Date: Mon,  5 Oct 2026 16:56:04 +0200	[thread overview]
Message-ID: <20261005145604.134614-1-mehmet.fide@gmail.com> (raw)

Hi,

please consider

  13221be72034 ("wifi: rtw88: Handle C2H_ADAPTIVITY in rtw_fw_c2h_cmd_handle()")

for the 6.6.y and 6.12.y stable trees. It is in mainline since 6.14 and
applies cleanly to both.

Without it rtw_fw_adaptivity_result() runs from the USB RX work: it
reads three registers as arguments of rtw_dbg(), which is an empty
inline when CONFIG_RTW88_DEBUG is off, so the reads still happen there.
Over USB a register read sleeps. On 6.12.112 with an RTL8822CU, the
only rtw88 chip with adaptivity support, this gave "Voluntary context
switch within RCU read-side critical section" in rtw_usb_rx_handler()
-> rtw_fw_c2h_cmd_rx_irqsafe() -> rtw_usb_read32() within a minute of
starting an AP, followed by "xHCI host controller not responding,
assume dead", which took every USB device on the board with it. With
the commit applied the same board ran the AP through a channel switch
test session without a message.

Thanks,
Mehmet

             reply	other threads:[~2026-10-05 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 14:56 Mehmet Fide [this message]
2026-10-06 21:35 ` Please apply 13221be72034 ("wifi: rtw88: Handle C2H_ADAPTIVITY in rtw_fw_c2h_cmd_handle()") to 6.6.y and 6.12.y Sasha Levin
2026-10-07  6:21   ` Mehmet Fide

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=20261005145604.134614-1-mehmet.fide@gmail.com \
    --to=mehmet.fide@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mehmet.fide@screeningeagle.com \
    --cc=pkshih@realtek.com \
    --cc=rtl8821cerfe2@gmail.com \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox