From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 381EECFD30C for ; Fri, 11 Oct 2024 09:56:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=twLU19o2sR3tQRyQU+W7/fwFa+c0iCJwdC/QX7FGVbs=; b=ztoa6x75UmvFSy DGex9DRVigsXVrGyItsKaAh+JbAQBGlaQuom9IevYXX7v0wgtSJwMYVH8JQio0x2kkD6tjLGxrYa2 d0puKMkCna1xqUDvuij9SrlFHzfG22kw0OIzV5Dg4ewSlzpvWxVT694l8LkgPxAsgaagEmDjug/Y3 7vNsrcNcvNCiF90Bo4Is9ydNUSxJ/Oz3GHSsREoS/Z4P9Jr40cu2BKmil5zrHGKOdYqefe0jFxYp0 BxxXct2p/yYerNOj18j6Lj3TkWfDK4q1PPFn9vp8bEltldsS0ymWmPKy6ojZA16QIbhdsjHqgTClL YxPN1S2WAlQMYwEa2MlQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1szCOE-0000000Ft9x-0xDl; Fri, 11 Oct 2024 09:56:54 +0000 Received: from gloria.sntech.de ([185.11.138.130]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1szCOB-0000000Ft9C-1o4u; Fri, 11 Oct 2024 09:56:52 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sntech.de; s=gloria202408; h=Content-Type:Content-Transfer-Encoding:MIME-Version: References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=ciLHEDlJFx/yBo6BbEQxX3v7o6dg6CNuVbDrI0ZaLuU=; b=rPrv72bIJD5WKQLxZ+70kkjCxd iDF4Uxk8GKYZ2jhuCMXiozqOn0qq689M9/EuMsegjYPiIULTPlJME8de90LGLPmS/PHZLdH5KzT1i XFMVNVkfB5/5kk7wOrUS0JmRBds+Nr4aON180g2F3wIYZucn2NkIOvitrICGCpY5p7o6285YGaTyi CIMb3NAW19VfqANZK6KCxHR0awuzYIXKcY6IUNTUEzAVN6K6CWYc1uXuvN4Z/KphI9wpKzaPYP/Cp brah8g5RCilRkadvT6RVZc8y39XRRYEtKB18QCyQlvQCqWPMsEkoqwpfZlh/xedpb3Obx3hcBNJXy Ql8Q+2nA==; Received: from i53875b34.versanet.de ([83.135.91.52] helo=diego.localnet) by gloria.sntech.de with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1szCO7-0005n5-Om; Fri, 11 Oct 2024 11:56:47 +0200 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: Jonas Karlman , Dragan Simic Cc: linux-rockchip@lists.infradead.org, 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: Fri, 11 Oct 2024 11:56:46 +0200 Message-ID: <1831993.TLkxdtWsSY@diego> In-Reply-To: <01e42e08965e58a337b9b531c10446fd@manjaro.org> References: <86ff39fe-cc88-4cf4-a1ad-6398a74ceb11@kwiboo.se> <01e42e08965e58a337b9b531c10446fd@manjaro.org> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20241011_025651_528384_CF018B76 X-CRM114-Status: GOOD ( 34.06 ) X-BeenThere: linux-rockchip@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Upstream kernel work for Rockchip platforms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Linux-rockchip" Errors-To: linux-rockchip-bounces+linux-rockchip=archiver.kernel.org@lists.infradead.org Am Freitag, 11. Oktober 2024, 11:04:38 CEST schrieb Dragan Simic: > Hello Jonas, > > On 2024-10-11 10:52, Jonas Karlman wrote: > > 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. > > > > This feel like a very aggressive limitation, to only allow the > > opp-suspend rate, that is not even used under normal load. > > > > I let my Rock Pi S board with a RK3308B variant run "stress -c 8" for > > around 10 hours and the reported temp only reach around 50-55 deg c, > > ambient temp around 20 deg c and board laying flat on a table without > > any enclosure or heat sink. > > > > This was running with performance as scaling_governor and cpu running > > the 1008000 opp. > > Thanks for testing all that! That's very low CPU temperature under > stress testing indeed. Maybe the cooling gets worse and the CPU > temperature goes higher if the board is installed into some small > enclosure with no natural or forced airflow? > > > Most RK3308 variants datasheets list 1.3 GHz as max rate for CPU, > > the K-variant lists 1.2 GHz, and the -S-variants seem to have both > > reduced voltage and max rate. > > > > The OPPs for this SoC already limits max rate to 1 GHz and is more than > > likely good enough to not reach the max temperature of 115-125 deg c as > > rated in datasheets and vendor DTs. > > > > Adding the tsadc and trips (same/similar as px30) will probably allow > > us > > to add/use the "missing" 1.2 and 1.3 GHz OPPs. > > With these insights, I agree that the patch might have been a bit > too extreme, but it also promotes good practices when it comes to > upstreaming. The general rule is not to add CPU or GPU OPPs with > no proper thermal configuration already in place. > > The patch has already been merged, and as I already noted, [1] I'll > try to implement, test and submit the proper thermal configuration > ASAP. It's up Heiko to decide whether to drop this patch or not. Hmm, interesting question ;-) . Dropping the patch is of course still possible and so far we haven't actually seen anyone with real-world problems. And with Jonas' stress test, it does look like nobody will in the (hopefully short) time till we have thermal management. @Dragan, if you're in favor of that I'll drop the patch. Heiko > > [1] > https://lore.kernel.org/linux-rockchip/df92710498f66bcb4580cb2cd1573fb2@manjaro.org/ > > >> Fixes: 6913c45239fd ("arm64: dts: rockchip: Add core dts for RK3308 > >> SOC") > >> Cc: stable@vger.kernel.org > >> Signed-off-by: Dragan Simic > >> --- > >> 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"; > >> }; > >> }; > _______________________________________________ Linux-rockchip mailing list Linux-rockchip@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-rockchip