From: Patrick DELAUNAY <patrick.delaunay@foss.st.com>
To: Mateusz Nowicki <mateusz.nowicki@posteo.net>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Valentin Caron <valentin.caron@foss.st.com>
Subject: Re: [PATCH] arm64: dts: st: add thermal zones on stm32mp251
Date: Wed, 7 Oct 2026 11:40:23 +0200 [thread overview]
Message-ID: <1a7f04c4-45c6-452b-a56b-0b2f32fc2dd8@foss.st.com> (raw)
In-Reply-To: <20261004121200.64034-1-mateusz.nowicki@posteo.net>
Hi,
in rules established by STMicroelectronics:
-Tcritical = Tj - (sensor tolerance). With Tj the function temperature.
-Tlimitation = 90% of Tcritical.
On STM32MP25, Tj=125C even if the overdrive is used. So we have:
- STM32MP2xxA/C/D/F, Tcritical = 125-3 = 122C
- STM32MP2xxA/C/D/F, Tlimitation = 110C
So critical value need to be adjusted to
temperature = <122000>;
hysteresis = <1000>;
On 10/4/26 14:12, Mateusz Nowicki wrote:
> Add a CPU and a SoC thermal zone for the two DTS sensors, each with a
> critical trip point at 120 degrees Celsius, below the 125 degrees
> Celsius max junction temperature of the STM32MP25.
>
> Signed-off-by: Mateusz Nowicki <mateusz.nowicki@posteo.net>
> ---
> arch/arm64/boot/dts/st/stm32mp251.dtsi | 28 ++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/st/stm32mp251.dtsi b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> index b624f998b87c..fd174c88b26d 100644
> --- a/arch/arm64/boot/dts/st/stm32mp251.dtsi
> +++ b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> @@ -158,6 +158,34 @@ RET_PD: power-domain-retention {
> };
> };
>
> + thermal-zones {
> + cpu-thermal {
polling-delay-passive = <250>;
because the DTS sensors have no interrupts support
> + polling-delay = <1000>;
> + thermal-sensors = <&dts 1>;
> +
> + trips {
> + cpu-crit {
> + temperature = <120000>;
> + hysteresis = <2000>;
temperature = <122000>;
hysteresis = <1000>;
> + type = "critical";
> + };
> + };
> + };
> +
> + soc-thermal {
polling-delay-passive = <250>;
> + polling-delay = <1000>;
> + thermal-sensors = <&dts 0>;
> +
> + trips {
> + soc-crit {
> + temperature = <120000>;
> + hysteresis = <2000>;
temperature = <122000>;
hysteresis = <1000>;
> + type = "critical";
> + };
> + };
> + };
> + };
> +
> timer {
> compatible = "arm,armv8-timer";
> interrupt-parent = <&intc>;
>
> base-commit: f831584128ac2a36fb4fa62fe106793d08c2dbf1
Regards
Patrick
prev parent reply other threads:[~2026-10-07 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 12:12 [PATCH] arm64: dts: st: add thermal zones on stm32mp251 Mateusz Nowicki
2026-10-07 9:40 ` Patrick DELAUNAY [this message]
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=1a7f04c4-45c6-452b-a56b-0b2f32fc2dd8@foss.st.com \
--to=patrick.delaunay@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mateusz.nowicki@posteo.net \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
--cc=valentin.caron@foss.st.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