From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: rafael@kernel.org, krzysztof.kozlowski+dt@linaro.org,
robh+dt@kernel.org, conor+dt@kernel.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
Fabio Estevam <festevam@denx.de>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v9 1/3] dt-bindings: thermal-zones: Document critical-action
Date: Sun, 1 Oct 2023 18:48:08 +0200 [thread overview]
Message-ID: <43ac7981-49d1-b1a3-c63e-5d304af9350b@linaro.org> (raw)
In-Reply-To: <20231001030014.1244633-1-festevam@gmail.com>
On 01/10/2023 05:00, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> Document the critical-action property to describe the thermal action
> the OS should perform after the critical temperature is reached.
>
> The possible values are "shutdown" and "reboot".
>
> The motivation for introducing the critical-action property is that
> different systems may need different thermal actions when the critical
> temperature is reached.
>
> For example, a desktop PC may want the OS to trigger a shutdown
> when the critical temperature is reached.
From my POV, 'critical' means kernel handles the action. We can not
trust the userspace at this point.
The 'hot' trip point will result on a notification to the OS which can
then take an last resort action before 'critical' kicks in (suspend,
kill process, cpu hotplug, whatever)
> However, in some embedded cases, such behavior does not suit well,
> as the board may be unattended in the field and rebooting may be a
> better approach.
>
> The bootloader may also benefit from this new property as it can check
> the SoC temperature and in case the temperature is above the critical
> point, it can trigger a shutdown or reboot accordingly.
>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> Changes since v8:
> - Go back to putting critical-action as a thermal-zone property. (Daniel)
>
> .../devicetree/bindings/thermal/thermal-zones.yaml | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/thermal/thermal-zones.yaml b/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
> index 4f3acdc4dec0..c2e4d28f885b 100644
> --- a/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
> +++ b/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
> @@ -75,6 +75,15 @@ patternProperties:
> framework and assumes that the thermal sensors in this zone
> support interrupts.
>
> + critical-action:
> + $ref: /schemas/types.yaml#/definitions/string
> + description:
> + The action the OS should perform after the critical temperature is reached.
> +
> + enum:
> + - shutdown
> + - reboot
> +
> thermal-sensors:
> $ref: /schemas/types.yaml#/definitions/phandle-array
> maxItems: 1
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2023-10-01 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 3:00 [PATCH v9 1/3] dt-bindings: thermal-zones: Document critical-action Fabio Estevam
2023-10-01 3:00 ` [PATCH v9 2/3] reboot: Introduce thermal_zone_device_critical_reboot() Fabio Estevam
2023-10-01 17:23 ` Daniel Lezcano
2023-10-01 3:00 ` [PATCH v9 3/3] thermal: thermal_core: Allow rebooting after critical temp Fabio Estevam
2023-10-01 17:25 ` Daniel Lezcano
2023-10-01 16:48 ` Daniel Lezcano [this message]
2023-10-01 17:09 ` [PATCH v9 1/3] dt-bindings: thermal-zones: Document critical-action 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=43ac7981-49d1-b1a3-c63e-5d304af9350b@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).