From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: "Sebastian Reichel" <sre@kernel.org>,
"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Zhang Rui" <rui.zhang@intel.com>,
"Lukasz Luba" <lukasz.luba@arm.com>,
linux-pm@vger.kernel.org, "Søren Andersen" <san@skov.dk>
Subject: Re: [PATCH v4 7/7] thermal: core: Record PSCR before hw_protection_shutdown()
Date: Wed, 12 Mar 2025 17:51:15 +0100 [thread overview]
Message-ID: <Z9G7g5fr8DkJtcLI@pengutronix.de> (raw)
In-Reply-To: <726c6ffc-a8d4-4328-a849-2d59f3a0a1c9@linaro.org>
Hi Daniel,
On Wed, Mar 12, 2025 at 04:35:51PM +0100, Daniel Lezcano wrote:
> > @@ -380,6 +381,8 @@ static void thermal_zone_device_halt(struct thermal_zone_device *tz, bool shutdo
> > dev_emerg(&tz->device, "%s: critical temperature reached\n", tz->type);
> > + set_power_state_change_reason(PSCR_OVERTEMPERATURE);
> > +
> > if (shutdown)
> > hw_protection_shutdown(msg, poweroff_delay_ms);
> > else
>
> In the future could you add me as recipient to the series instead of this
> one ? so I can get more context.
ack.
> Given there are no so much hw_protection_shutdown() users in the kernel, it
> could be more interesting to change the function to receive a enum
> pscr_reason and then in the hw_protection_shutdown() call
> pscrr_reason_to_str().
Do you mean, make it work with CONFIG_PSCRR=n?
Beside, the latest version is v5:
https://lore.kernel.org/all/20250310103732.423542-1-o.rempel@pengutronix.de/
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-03-12 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 9:38 [PATCH v4 0/7] Introduction of PSCR Framework and Related Components Oleksij Rempel
2025-03-06 9:38 ` [PATCH v4 1/7] power: Extend power_on_reason.h for upcoming PSCRR framework Oleksij Rempel
2025-03-06 9:38 ` [PATCH v4 2/7] power: reset: Introduce PSCR Recording Framework for Non-Volatile Storage Oleksij Rempel
2025-03-06 9:38 ` [PATCH v4 3/7] nvmem: provide consumer access to cell size metrics Oleksij Rempel
2025-03-06 9:38 ` [PATCH v4 4/7] nvmem: add support for device and sysfs-based cell lookups Oleksij Rempel
2025-03-07 12:35 ` kernel test robot
2025-03-07 15:04 ` kernel test robot
2025-03-08 17:06 ` kernel test robot
2025-03-06 9:38 ` [PATCH v4 5/7] power: reset: add PSCR NVMEM Driver for Recording Power State Change Reasons Oleksij Rempel
2025-03-06 9:38 ` [PATCH v4 6/7] regulator: set Power State Change Reason before hw_protection_shutdown() Oleksij Rempel
2025-03-06 9:38 ` [PATCH v4 7/7] thermal: core: Record PSCR " Oleksij Rempel
2025-03-12 15:35 ` Daniel Lezcano
2025-03-12 16:51 ` Oleksij Rempel [this message]
2025-03-12 17:22 ` Daniel Lezcano
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=Z9G7g5fr8DkJtcLI@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=broonie@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=kernel@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=san@skov.dk \
--cc=sre@kernel.org \
--cc=srinivas.kandagatla@linaro.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