From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Kalpesh Solanki" <skalpesh942@gmail.com>
Cc: pkshih@realtek.com, kvalo@kernel.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
"Kalpesh Solanki" <skalpesh942@gmail.com>
Subject: Re: [PATCH v2 2/2] wifi: rtw88: ps: Trigger firmware recovery when failing to leave LPS state
Date: Sat, 07 Nov 2026 07:48:01 +0000 [thread overview]
Message-ID: <d7e20cc5e8a0489b9b22f13a9fe8a1b423d2f8f1@linux.dev> (raw)
In-Reply-To: <20261107063141.25442-1-skalpesh942@gmail.com>
Hi Kalpesh,
Thanks for the quick reply. I just have a few things to add.
[ ... ]
> Clearing RTW_FLAG_RESTARTING (and resetting the hang counter) in
> rtw_ops_stop() sounds like the right way to handle it.
That is fine for the flag, but I think the counter should be reset in
rtw_core_start(), like rtw89 does. A normal recovery never calls
rtw_ops_stop(), so the counter would stay at the limit and the next
single timeout would recover again.
> I can prepare a 2-patch follow-up series:
> 1. wifi: rtw88: ps: trigger recovery only after consecutive LPS leave failures
> 2. wifi: rtw88: clear RTW_FLAG_RESTARTING in rtw_ops_stop()
The RESTARTING gap predates your patch, since 5c831644e1f4 ("rtw88:
handle and recover when firmware crash"), so that one could go on its
own with a Fixes: tag.
For the counter, maybe it is cleaner to revert 2/2 (or rebase and drop
it since it is currently the HEAD commit of rtw-next) and send a new
patch, since it replaces that line anyway and keeps the current
behavior out of the next pull. 1/2 is fine as it is. Ping-Ke, would
that work for you, or do you prefer a follow up?
Also Kalpesh, your replies don't carry In-Reply-To or References, so
lore shows them as separate threads. In case you are using git send-email
git send-email --in-reply-to=<Message-ID>
should fix that.
Best regards,
Luka Gejak
next prev parent reply other threads:[~2026-11-07 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 6:31 [PATCH v2 2/2] wifi: rtw88: ps: Trigger firmware recovery when failing to leave LPS state Kalpesh Solanki
2026-11-07 7:48 ` Luka Gejak [this message]
2026-11-07 8:16 ` Kalpesh Solanki
2026-11-08 3:20 ` Ping-Ke Shih
-- strict thread matches above, loose matches on Subject: below --
2026-11-03 3:14 [PATCH v2 1/2] wifi: rtw88: pci: Add DMI quirk for HP Laptop 15s-fr5xxx Kalpesh Solanki
2026-11-03 3:14 ` [PATCH v2 2/2] wifi: rtw88: ps: Trigger firmware recovery when failing to leave LPS state Kalpesh Solanki
2026-11-03 3:17 ` Ping-Ke Shih
2026-11-06 15:33 ` Luka Gejak
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=d7e20cc5e8a0489b9b22f13a9fe8a1b423d2f8f1@linux.dev \
--to=luka.gejak@linux.dev \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=skalpesh942@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 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.