From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: Add idle cooling devices
Date: Sun, 17 Oct 2021 21:51:53 +0200 [thread overview]
Message-ID: <30f0cbda-5172-6af1-c06d-2e9c4b96d46b@linaro.org> (raw)
In-Reply-To: <2808512.kKcWQYovEV@phil>
Hi Heiko,
On 17/10/2021 12:13, Heiko Stuebner wrote:
> Hi Daniel,
>
> Am Freitag, 1. Oktober 2021, 18:17:28 CEST schrieb Daniel Lezcano:
>> The thermal framework accepts now the cpu idle cooling device as an
>> alternative when the cpufreq cooling device fails.
>>
>> Add the node in the DT so the cooling devices will be present and the
>> platforms can extend the thermal zone definition to add them.
>>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>> ---
>> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> index 3871c7fd83b0..9ac232ffd284 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> @@ -124,6 +124,11 @@ cpu_b0: cpu@100 {
>> #cooling-cells = <2>; /* min followed by max */
>> dynamic-power-coefficient = <436>;
>> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
>> + thermal-idle {
>> + #cooling-cells = <2>;
>> + duration-us = <10000>;
>> + exit-latency-us = <500>;
>> + };
>
> I guess the basic question would be where do the duration
> and exit-latency values come from. And also what happened
> to cpu_l0-l3 (aka the little cores)?
The duration is an arbitrary value, I've done some testing [1] to cool
down the CPU.
The exit-latency is a value to ignore idle states with greater exit
latency. In our case, it discards the cluster power down state.
My experiments on this platform showed the little cluster does not
contribute significantly to the heat, so having idle injection is not
really useful.
Just to clarify that idle injection is not better than dvfs, it can be
used in addition or as a backup solution if the dvfs fails. That is the
reason why there is no setup for the thermal zones.
[1] https://www.linaro.org/blog/force-idle-when-a-cpu-is-overheating/
>> };
>>
>> cpu_b1: cpu@101 {
>> @@ -136,6 +141,11 @@ cpu_b1: cpu@101 {
>> #cooling-cells = <2>; /* min followed by max */
>> dynamic-power-coefficient = <436>;
>> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
>> + thermal-idle {
>> + #cooling-cells = <2>;
>> + duration-us = <10000>;
>> + exit-latency-us = <500>;
>> + };
>> };
>>
>> idle-states {
>>
>
>
>
>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2021-10-17 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 16:17 [PATCH] arm64: dts: rockchip: Add idle cooling devices Daniel Lezcano
2021-10-17 10:13 ` Heiko Stuebner
2021-10-17 19:51 ` Daniel Lezcano [this message]
2021-10-20 8:01 ` Heiko Stuebner
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=30f0cbda-5172-6af1-c06d-2e9c4b96d46b@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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).