From: Dragan Simic <dsimic@manjaro.org>
To: linux-rockchip@lists.infradead.org
Cc: heiko@sntech.de, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: Prevent thermal runaways in RK3308 SoC dtsi
Date: Thu, 10 Oct 2024 18:04:18 +0200 [thread overview]
Message-ID: <df92710498f66bcb4580cb2cd1573fb2@manjaro.org> (raw)
In-Reply-To: <d3e9dc4201d38894b09f3198368428153a3af1a4.1728555461.git.dsimic@manjaro.org>
On 2024-10-10 12:19, Dragan Simic wrote:
> Until the TSADC, thermal zones, thermal trips and cooling maps are
> defined
> in the RK3308 SoC dtsi, none of the CPU OPPs except the slowest one may
> be
> enabled under any circumstances. Allowing the DVFS to scale the CPU
> cores
> up without even just the critical CPU thermal trip in place can rather
> easily
> result in thermal runaways and damaged SoCs, which is bad.
>
> Thus, leave only the lowest available CPU OPP enabled for now.
>
> Fixes: 6913c45239fd ("arm64: dts: rockchip: Add core dts for RK3308
> SOC")
> Cc: stable@vger.kernel.org
> Signed-off-by: Dragan Simic <dsimic@manjaro.org>
As a note, I'll hopefully get back with the proper implementation of the
thermal configuration for the RK3308, but not before the 6.14 merge
window.
In the meantime, let's stick to having only the lowest CPU OPP in place,
as changed in this patch.
> ---
> arch/arm64/boot/dts/rockchip/rk3308.dtsi | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3308.dtsi
> b/arch/arm64/boot/dts/rockchip/rk3308.dtsi
> index 31c25de2d689..a7698e1f6b9e 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3308.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3308.dtsi
> @@ -120,16 +120,19 @@ opp-600000000 {
> opp-hz = /bits/ 64 <600000000>;
> opp-microvolt = <950000 950000 1340000>;
> clock-latency-ns = <40000>;
> + status = "disabled";
> };
> opp-816000000 {
> opp-hz = /bits/ 64 <816000000>;
> opp-microvolt = <1025000 1025000 1340000>;
> clock-latency-ns = <40000>;
> + status = "disabled";
> };
> opp-1008000000 {
> opp-hz = /bits/ 64 <1008000000>;
> opp-microvolt = <1125000 1125000 1340000>;
> clock-latency-ns = <40000>;
> + status = "disabled";
> };
> };
next prev parent reply other threads:[~2024-10-10 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 10:19 [PATCH] arm64: dts: rockchip: Prevent thermal runaways in RK3308 SoC dtsi Dragan Simic
2024-10-10 16:04 ` Dragan Simic [this message]
2024-10-10 17:32 ` Trevor Woerner
2024-10-10 20:27 ` Heiko Stuebner
2024-10-11 16:35 ` Heiko Stübner
2024-10-11 8:52 ` Jonas Karlman
2024-10-11 9:04 ` Dragan Simic
2024-10-11 9:56 ` Heiko Stübner
2024-10-11 10:09 ` Dragan Simic
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=df92710498f66bcb4580cb2cd1573fb2@manjaro.org \
--to=dsimic@manjaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=stable@vger.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).