From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>,
John Madieu <john.madieu.xa@bp.renesas.com>,
"Rafael J . Wysocki" <rafael@kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] thermal: rzg3e: Propagate reset assertion failure from suspend
Date: Tue, 29 Sep 2026 13:57:45 +0200 [thread overview]
Message-ID: <ef9d2842-1e98-4f40-8aa1-307f63f62b5b@oss.qualcomm.com> (raw)
In-Reply-To: <20260828092123.9707-1-pengpeng@iscas.ac.cn>
On 8/28/26 11:21, Pengpeng Hou wrote:
> rzg3e_thermal_suspend() powers off an active sensor and then ignores
> failure to assert its reset. System sleep can therefore continue
> without the clean reset state expected by resume.
>
> Return the reset error and, when the sensor had been active, try to
> restore power before failing suspend. This remains an RFC because a
> reset assertion failure can represent partial hardware state and the
> preferred recovery policy needs platform confirmation.
>
> The issue was identified via static analysis and manually reviewed.
>
> Assisted-by: LLM
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
> ---
Please resend without the RFC prefix and with Claudiu tag
Thanks
prev parent reply other threads:[~2026-09-29 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 9:21 Pengpeng Hou
2026-09-28 16:36 ` Daniel Lezcano
2026-09-29 10:39 ` claudiu beznea
2026-09-29 11:57 ` Daniel Lezcano [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=ef9d2842-1e98-4f40-8aa1-307f63f62b5b@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=daniel.lezcano@kernel.org \
--cc=john.madieu.xa@bp.renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=pengpeng@iscas.ac.cn \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.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®