From: Johan Hovold <johan@kernel.org>
To: Stephan Gerhold <stephan.gerhold@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Abel Vesa <abel.vesa@linaro.org>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Akhil P Oommen <quic_akhilpo@quicinc.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: [PATCH 2/4] arm64: dts: qcom: x1e80100: Apply consistent critical thermal shutdown
Date: Wed, 19 Feb 2025 16:36:45 +0100 [thread overview]
Message-ID: <Z7X6jZev8fpoq0Ih@hovoldconsulting.com> (raw)
In-Reply-To: <20250219-x1e80100-thermal-fixes-v1-2-d110e44ac3f9@linaro.org>
On Wed, Feb 19, 2025 at 12:36:19PM +0100, Stephan Gerhold wrote:
> The firmware configures the TSENS controller with a maximum temperature of
> 120°C. When reaching that temperature, the hardware automatically triggers
> a reset of the entire platform. Some of the thermal zones in x1e80100.dtsi
> use a critical trip point of 125°C. It's impossible to reach those.
>
> It's preferable to shut down the system cleanly before reaching the
> hardware trip point. Make the critical temperature trip points consistent
> by setting all of them to 115°C and apply a consistent hysteresis.
> The ACPI tables also specify 115°C as critical shutdown temperature.
>
> Cc: stable@vger.kernel.org
> Fixes: 4e915987ff5b ("arm64: dts: qcom: x1e80100: Enable tsens and thermal zone nodes")
> Signed-off-by: Stephan Gerhold <stephan.gerhold@linaro.org>
> @@ -8483,7 +8483,7 @@ trip-point1 {
> };
>
> cpu-critical {
> - temperature = <110000>;
> + temperature = <115000>;
Have you asked the authors where this lower limit came from (or
determined it was just copy pasta some other way)?
> hysteresis = <1000>;
> type = "critical";
> };
> @@ -8737,7 +8737,7 @@ trip-point0 {
> };
>
> video-critical {
> - temperature = <125000>;
> + temperature = <115000>;
> hysteresis = <1000>;
> type = "critical";
> };
Ok, make sense to backport the first patch as well then.
Looks good to me:
Reviewed-by: Johan Hovold <johan+linaro@kernel.org>
next prev parent reply other threads:[~2025-02-19 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 11:36 [PATCH 0/4] arm64: dts: qcom: x1e80100: Fix thermal trip points Stephan Gerhold
2025-02-19 11:36 ` [PATCH 1/4] arm64: dts: qcom: x1e80100: Fix video thermal zone Stephan Gerhold
2025-02-19 15:28 ` Johan Hovold
2025-02-19 16:22 ` Stephan Gerhold
2025-02-20 12:54 ` Konrad Dybcio
2025-02-19 11:36 ` [PATCH 2/4] arm64: dts: qcom: x1e80100: Apply consistent critical thermal shutdown Stephan Gerhold
2025-02-19 15:36 ` Johan Hovold [this message]
2025-02-19 16:28 ` Stephan Gerhold
2025-02-20 12:55 ` Konrad Dybcio
2025-02-19 11:36 ` [PATCH 3/4] arm64: dts: qcom: x1e80100: Add GPU cooling Stephan Gerhold
2025-02-19 15:42 ` Johan Hovold
2025-02-21 19:35 ` Konrad Dybcio
2025-02-19 11:36 ` [PATCH 4/4] arm64: dts: qcom: x1e80100: Drop unused passive thermal trip points for CPU Stephan Gerhold
2025-02-19 15:47 ` Johan Hovold
2025-02-21 19:36 ` Konrad Dybcio
2025-03-04 17:00 ` [PATCH 0/4] arm64: dts: qcom: x1e80100: Fix thermal trip points Bjorn Andersson
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=Z7X6jZev8fpoq0Ih@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_akhilpo@quicinc.com \
--cc=quic_rjendra@quicinc.com \
--cc=robh@kernel.org \
--cc=stephan.gerhold@linaro.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