From: Kalpesh Solanki <skalpesh942@gmail.com>
To: pkshih@realtek.com
Cc: luka.gejak@linux.dev, kvalo@kernel.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Kalpesh Solanki <skalpesh942@gmail.com>
Subject: [PATCH v3 0/2] wifi: rtw88: firmware recovery fixes and LPS hang handling
Date: Sun, 8 Nov 2026 14:21:23 +0530 [thread overview]
Message-ID: <20261108085126.331784-1-skalpesh942@gmail.com> (raw)
This series addresses firmware recovery issues in rtw88.
Patch 1/2 from the v2 series (DMI quirk for HP Laptop 15s-fr5xxx) was
already applied to rtw-next. In this v3 series, patch 2/2 is replaced
and an additional fix is included based on feedback from Luka Gejak:
1. Patch 1/2 clears RTW_FLAG_RESTARTING in rtw_ops_stop() to fix a
pre-existing bug where recovery remains permanently disabled if the
interface is stopped or suspended before drv_reconfig_complete() is
called.
2. Patch 2/2 replaces the previous LPS leave recovery change: instead
of immediately triggering hardware restart on a single timeout (which
causes spurious resets on noisy links or beacon loss), it introduces
a consecutive hang counter (RTW_PS_HANG_MAX_CNT = 3) matching rtw89.
The counter is reset on success and in rtw_core_start().
Changes in v3:
- Note: v2 patch 1/2 (DMI quirk) is already applied in rtw-next.
- Add patch 1/2 to clear RTW_FLAG_RESTARTING in rtw_ops_stop()
with Fixes tag.
- In patch 2/2:
- Count consecutive failures before triggering recovery
(RTW_PS_HANG_MAX_CNT = 3).
- Reset ps_hang_cnt on successful LPS leave and in rtw_core_start().
- Suppress raw register dump on transient failures to avoid log spam.
Kalpesh Solanki (2):
wifi: rtw88: clear RTW_FLAG_RESTARTING in rtw_ops_stop()
wifi: rtw88: ps: trigger firmware recovery only after consecutive LPS
leave failures
drivers/net/wireless/realtek/rtw88/mac80211.c | 1 +
drivers/net/wireless/realtek/rtw88/main.c | 2 ++
drivers/net/wireless/realtek/rtw88/main.h | 1 +
drivers/net/wireless/realtek/rtw88/ps.c | 9 ++++++++-
drivers/net/wireless/realtek/rtw88/ps.h | 1 +
5 files changed, 13 insertions(+), 1 deletion(-)
--
2.53.0
next reply other threads:[~2026-11-08 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 8:51 Kalpesh Solanki [this message]
2026-11-08 8:51 ` [PATCH v3 1/2] wifi: rtw88: clear RTW_FLAG_RESTARTING in rtw_ops_stop() Kalpesh Solanki
2026-11-08 8:51 ` [PATCH v3 2/2] wifi: rtw88: ps: trigger firmware recovery only after consecutive LPS leave failures Kalpesh Solanki
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=20261108085126.331784-1-skalpesh942@gmail.com \
--to=skalpesh942@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--cc=pkshih@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
all inboxes | Powered by JetHome®