All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: daniel.lezcano@linaro.org
Cc: rafael@kernel.org, amitk@kernel.org, rui.zhang@intel.com,
	linux-pm@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
	robh+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, Fabio Estevam <festevam@denx.de>
Subject: [PATCH 2/4] dt-bindings: thermal: Document the values for the 'critical-action'
Date: Fri, 25 Aug 2023 07:24:51 -0300	[thread overview]
Message-ID: <20230825102453.836627-2-festevam@gmail.com> (raw)
In-Reply-To: <20230825102453.836627-1-festevam@gmail.com>

From: Fabio Estevam <festevam@denx.de>

Document the possible values for the 'critical-action' property to make
it more readable in the devicetree.

Signed-off-by: Fabio Estevam <festevam@denx.de>
---
 include/dt-bindings/thermal/thermal.h | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/include/dt-bindings/thermal/thermal.h b/include/dt-bindings/thermal/thermal.h
index bc7babb1a67c..f433b6b0ffb7 100644
--- a/include/dt-bindings/thermal/thermal.h
+++ b/include/dt-bindings/thermal/thermal.h
@@ -12,5 +12,9 @@
 /* On cooling devices upper and lower limits */
 #define THERMAL_NO_LIMIT		(~0)
 
+/* Possible values for the 'critical-action' property */
+#define THERMAL_CRITICAL_ACTION_SHUTDOWN	0
+#define THERMAL_CRITICAL_ACTION_REBOOT		1
+
 #endif
 
-- 
2.34.1


  reply	other threads:[~2023-08-25 10:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 10:24 [PATCH 1/4] dt-bindings: thermal-zones: Document critical-action Fabio Estevam
2023-08-25 10:24 ` Fabio Estevam [this message]
2023-08-25 10:24 ` [PATCH 3/4] reboot: Introduce hw_protection_reboot() Fabio Estevam
2023-08-25 10:24 ` [PATCH 4/4] thermal: thermal_core: Allow rebooting after critical temp Fabio Estevam

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=20230825102453.836627-2-festevam@gmail.com \
    --to=festevam@gmail.com \
    --cc=amitk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@denx.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=robh+dt@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 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.