From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org> To: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org> Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org Subject: Re: [PATCH] arm64: dts: rockchip: Fix NanoPC-T4 cooling maps Date: Mon, 18 Nov 2019 01:52:39 +0100 [thread overview] Message-ID: <4249681.hKoAvgd4aH@phil> (raw) In-Reply-To: <5bb39f3115df1a487d717d3ae87e523b03749379.1573908197.git.robin.murphy-5wv7dgnIgG8@public.gmane.org> Am Samstag, 16. November 2019, 13:47:19 CET schrieb Robin Murphy: > Although it appeared to follow logically from the bindings, apparently > the thermal framework can't properly cope with a single cooling device > being shared between multiple maps. The CPU zone is probably easier to > overheat, so remove the references to the (optional) fan from the GPU > cooling zone to avoid things getting confused. Hopefully GPU-intensive > tasks will leak enough heat across to the CPU zone to still hit the > fan trips before reaching critical GPU temperatures. > > Signed-off-by: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org> applied, after little bit of editing. > &i2s0 { > status = "okay"; > }; although my nano-pc dts does not seem to have that &i2s0 node yet. Did I miss a patch somewhere? Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de> To: Robin Murphy <robin.murphy@arm.com> Cc: linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] arm64: dts: rockchip: Fix NanoPC-T4 cooling maps Date: Mon, 18 Nov 2019 01:52:39 +0100 [thread overview] Message-ID: <4249681.hKoAvgd4aH@phil> (raw) In-Reply-To: <5bb39f3115df1a487d717d3ae87e523b03749379.1573908197.git.robin.murphy@arm.com> Am Samstag, 16. November 2019, 13:47:19 CET schrieb Robin Murphy: > Although it appeared to follow logically from the bindings, apparently > the thermal framework can't properly cope with a single cooling device > being shared between multiple maps. The CPU zone is probably easier to > overheat, so remove the references to the (optional) fan from the GPU > cooling zone to avoid things getting confused. Hopefully GPU-intensive > tasks will leak enough heat across to the CPU zone to still hit the > fan trips before reaching critical GPU temperatures. > > Signed-off-by: Robin Murphy <robin.murphy@arm.com> applied, after little bit of editing. > &i2s0 { > status = "okay"; > }; although my nano-pc dts does not seem to have that &i2s0 node yet. Did I miss a patch somewhere? Heiko _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-18 0:52 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-16 12:47 [PATCH] arm64: dts: rockchip: Fix NanoPC-T4 cooling maps Robin Murphy 2019-11-16 12:47 ` Robin Murphy [not found] ` <5bb39f3115df1a487d717d3ae87e523b03749379.1573908197.git.robin.murphy-5wv7dgnIgG8@public.gmane.org> 2019-11-18 0:52 ` Heiko Stuebner [this message] 2019-11-18 0:52 ` Heiko Stuebner 2019-11-18 12:09 ` Robin Murphy 2019-11-18 12:09 ` Robin Murphy
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=4249681.hKoAvgd4aH@phil \ --to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \ --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=robin.murphy-5wv7dgnIgG8@public.gmane.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.