From: Chrispine Tinega <dev@chrispinetinega.com>
To: Lee Jones <lee@kernel.org>
Cc: lgirdwood@gmail.com, broonie@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, aaro.koskinen@iki.fi,
andreas@kemnade.info, khilman@baylibre.com, rogerq@kernel.org,
tony@atomide.com, jerome.neanne@baylibre.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, mfd@lists.linux.dev,
Chrispine Tinega <dev@chrispinetinega.com>
Subject: [PATCH v2 2/3] regulator: dt-bindings: ti,tps65219: Add ti,no-warm-shutdown
Date: Mon, 16 Nov 2026 21:58:10 +0300 [thread overview]
Message-ID: <20261116185811.1907811-3-dev@chrispinetinega.com> (raw)
In-Reply-To: <20261116185811.1907811-1-dev@chrispinetinega.com>
The TPS65219 has four die temperature sensors, each with a warm and a
hot threshold. A sensor whose warm warning is not masked makes the PMIC
sequence all its outputs down at the warm threshold, 110 to 130 C.
Masked, the warning is only reported, and the PMIC powers off at the hot
threshold, 130 to 150 C. Whether a board can run past the warm threshold
depends on its thermal design, so the board's devicetree has to say so.
Add ti,no-warm-shutdown for that. It is allowed on the TPS65219 only:
the masks are not described here for the TPS65214 and TPS65215.
Signed-off-by: Chrispine Tinega <dev@chrispinetinega.com>
Reviewed-by: Mark Brown <broonie@kernel.org>
---
Changes in v2:
- Drop "so the board can run warmer and the operating system decides
how to react to the warning" from the description. Nothing acts on
the warning today. (Mark)
- Add Mark's Reviewed-by.
.../devicetree/bindings/regulator/ti,tps65219.yaml | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree/bindings/regulator/ti,tps65219.yaml b/Documentation/devicetree/bindings/regulator/ti,tps65219.yaml
index 7c64e588a..22aea7f61 100644
--- a/Documentation/devicetree/bindings/regulator/ti,tps65219.yaml
+++ b/Documentation/devicetree/bindings/regulator/ti,tps65219.yaml
@@ -62,6 +62,15 @@ properties:
where the board has a button wired to the pin and triggers
an interrupt on pressing it.
+ ti,no-warm-shutdown:
+ type: boolean
+ description: |
+ Keep the PMIC running when one of its die temperature sensors passes
+ its warm threshold. By default, a sensor whose warm warning is not
+ masked makes the PMIC sequence all its outputs down at that
+ threshold. With this property the warning is only reported, and the
+ PMIC powers off at its hot threshold instead.
+
regulators:
type: object
description: |
@@ -111,6 +120,7 @@ allOf:
- ti,tps65215
then:
properties:
+ ti,no-warm-shutdown: false
regulators:
patternProperties:
"^ldo[3-4]$": false
--
2.53.0
next prev parent reply other threads:[~2026-11-16 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 18:58 [PATCH v2 0/3] mfd: tps65219: Let a board run past the warm threshold Chrispine Tinega
2026-11-16 18:58 ` [PATCH v2 1/3] mfd: tps65219: Correct the MASK_EFFECT field of MASK_CONFIG Chrispine Tinega
2026-11-16 18:58 ` Chrispine Tinega [this message]
2026-11-16 18:58 ` [PATCH v2 3/3] mfd: tps65219: Keep running past the warm threshold when asked Chrispine Tinega
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=20261116185811.1907811-3-dev@chrispinetinega.com \
--to=dev@chrispinetinega.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jerome.neanne@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=tony@atomide.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®