From: "Heiko Stübner" <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org, Dragan Simic <dsimic@manjaro.org>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: rockchip: Prevent thermal runaways in RK3308 SoC dtsi
Date: Fri, 11 Oct 2024 18:35:11 +0200 [thread overview]
Message-ID: <3125164.CbtlEUcBR6@diego> (raw)
In-Reply-To: <172859192266.2746127.3378168630215627036.b4-ty@sntech.de>
Am Donnerstag, 10. Oktober 2024, 22:27:44 CEST schrieb Heiko Stuebner:
> On Thu, 10 Oct 2024 12:19:41 +0200, 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.
> >
> > [...]
>
> Applied, thanks!
>
> [1/1] arm64: dts: rockchip: Prevent thermal runaways in RK3308 SoC dtsi
> commit: 864f1a5b390278a4a8d4a6d7425c7022477c6c9f
as discussed in the other replies, I've dropped the patch again
Heiko
next prev parent reply other threads:[~2024-10-11 16:35 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
2024-10-10 17:32 ` Trevor Woerner
2024-10-10 20:27 ` Heiko Stuebner
2024-10-11 16:35 ` Heiko Stübner [this message]
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=3125164.CbtlEUcBR6@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--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).