From: "Rob Herring (Arm)" <robh@kernel.org>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Fabio Estevam <festevam@denx.de>,
kernel@pengutronix.de, Lukasz Luba <lukasz.luba@arm.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Tzung-Bi Shih <tzungbi@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-pm@vger.kernel.org,
Daniel Lezcano <daniel.lezcano@linaro.org>,
chrome-platform@lists.linux.dev,
Guenter Roeck <groeck@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Benson Leung <bleung@chromium.org>,
linux-security-module@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
devicetree@vger.kernel.org, Serge Hallyn <serge@hallyn.com>,
Zhang Rui <rui.zhang@intel.com>, Mark Brown <broonie@kernel.org>,
Matti Vaittinen <mazziesaccount@gmail.com>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 09/11] dt-bindings: thermal: give OS some leeway in absence of critical-action
Date: Thu, 2 Jan 2025 11:33:34 -0600 [thread overview]
Message-ID: <173583921303.72780.9548337351300599303.robh@kernel.org> (raw)
In-Reply-To: <20241219-hw_protection-reboot-v1-9-263a0c1df802@pengutronix.de>
On Thu, 19 Dec 2024 08:31:30 +0100, Ahmad Fatoum wrote:
> An operating system may allow its user to configure the action to be
> undertaken on critical overtemperature events.
>
> However, the bindings currently mandate an absence of the critical-action
> property to be equal to critical-action = "shutdown", which would mean
> any differing user configuration would violate the bindings.
>
> Resolve this by documenting the absence of the property to mean that the
> OS gets to decide.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> Documentation/devicetree/bindings/thermal/thermal-zones.yaml | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-01-02 17:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 7:31 [PATCH 00/11] reboot: support runtime configuration of emergency hw_protection action Ahmad Fatoum
2024-12-19 7:31 ` [PATCH 01/11] reboot: replace __hw_protection_shutdown bool action parameter with an enum Ahmad Fatoum
2024-12-19 7:31 ` [PATCH 02/11] reboot: reboot, not shutdown, on hw_protection_reboot timeout Ahmad Fatoum
2024-12-20 6:12 ` kernel test robot
2025-01-06 14:28 ` Ahmad Fatoum
2024-12-19 7:31 ` [PATCH 03/11] docs: thermal: sync hardware protection doc with code Ahmad Fatoum
2024-12-19 7:31 ` [PATCH 04/11] reboot: rename now misleading hw_protection symbols Ahmad Fatoum
2024-12-20 6:56 ` kernel test robot
2024-12-19 7:31 ` [PATCH 05/11] reboot: indicate whether it is a HARDWARE PROTECTION reboot or shutdown Ahmad Fatoum
2024-12-19 7:31 ` [PATCH 06/11] reboot: add support for configuring emergency hardware protection action Ahmad Fatoum
2024-12-19 7:31 ` [PATCH 07/11] regulator: allow user configuration of " Ahmad Fatoum
2024-12-19 7:31 ` [PATCH 08/11] platform/chrome: cros_ec_lpc: prepare for hw_protection_shutdown removal Ahmad Fatoum
2024-12-19 7:31 ` [PATCH 09/11] dt-bindings: thermal: give OS some leeway in absence of critical-action Ahmad Fatoum
2025-01-02 17:33 ` Rob Herring (Arm) [this message]
2024-12-19 7:31 ` [PATCH 10/11] thermal: core: allow user configuration of hardware protection action Ahmad Fatoum
2024-12-19 7:31 ` [PATCH 11/11] reboot: retire hw_protection_reboot and hw_protection_shutdown helpers Ahmad Fatoum
2024-12-22 9:38 ` [PATCH 00/11] reboot: support runtime configuration of emergency hw_protection action Matti Vaittinen
2024-12-22 9:58 ` Ahmad Fatoum
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=173583921303.72780.9548337351300599303.robh@kernel.org \
--to=robh@kernel.org \
--cc=a.fatoum@pengutronix.de \
--cc=bleung@chromium.org \
--cc=broonie@kernel.org \
--cc=chrome-platform@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=groeck@chromium.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mazziesaccount@gmail.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=serge@hallyn.com \
--cc=tzungbi@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).