From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Ondřej Jirman" <megous@megous.com>,
linux-sunxi@googlegroups.com, "Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Chen-Yu Tsai" <wens@csie.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:ARM/Allwinner sunXi SoC support"
<linux-arm-kernel@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: dts: sun8i-a83t: Add thermal trip points/cooling maps
Date: Mon, 24 Feb 2020 18:56:18 +0100 [thread overview]
Message-ID: <25a5dfb2-93bb-90c3-8156-0cfbed1f9995@linaro.org> (raw)
In-Reply-To: <20200224173940.huwpaqhrc5ngbmji@core.my.home>
On 24/02/2020 18:39, Ondřej Jirman wrote:
> On Mon, Feb 24, 2020 at 06:23:28PM +0100, megous hlavni wrote:
>> Hi,
>>
>> On Mon, Feb 24, 2020 at 06:06:20PM +0100, Daniel Lezcano wrote:
>>> On 24/02/2020 17:54, Ondrej Jirman wrote:
>>>> This enables passive cooling by down-regulating CPU voltage
>>>> clocks = <&ccu CLK_C1CPUX>;
>>>> @@ -1188,12 +1188,60 @@ cpu0_thermal: cpu0-thermal {
>>>> polling-delay-passive = <0>;
>>>> polling-delay = <0>;
>>>> thermal-sensors = <&ths 0>;
>>>> +
>>>> + trips {
>>>> + ': cpu-hot {
>>>> + temperature = <80000>;
>>>> + hysteresis = <2000>;
>>>> + type = "passive";
>>>> + };
>>>> +
>>>> + cpu0_very_hot: cpu-very-hot {
>>>> + temperature = <100000>;
>>>> + hysteresis = <0>;
>>>> + type = "critical";
>>>> + };
>>>> + };
>>>> +
>>>> + cooling-maps {
>>>> + cpu-hot-limit {
>>>> + trip = <&cpu0_hot>;
>>>> + cooling-device = <&cpu0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
>>>> + <&cpu1 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
>>>> + <&cpu2 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
>>>> + <&cpu3 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
>>>> + };
>>>> + };
>>>> };
>>>>
>>>> cpu1_thermal: cpu1-thermal {
>>>> polling-delay-passive = <0>;
>>>
>>> No polling to mitigate?
>>
>> Polling to mitigate what?
>>
>> The driver is using interrupts whenever new reading is available, and
>> notifies tz of the change. I don't have a reason to believe any new
>> values are available from thermal sensor outside of the interrupt
>> period.
>
> To be more clear, new temperatures are available from the thermal sensor driver
> at the rate of 4 per second, which should be enough to do quick adjustments to
> the thermal zone/cooling device even for quick temperature rises.
>
> https://elixir.bootlin.com/linux/v5.6-rc3/source/drivers/thermal/sun8i_thermal.c#L442
>
> There's no slow/fast period depending on whether the cooling is active.
> It's always fast and no polling of the thermal sensor is needed.
Thanks for the clarification. All sensors have their specificity.
Does the sensor allow to create a threshold temperature where an
interrupt fires when crossing the boundary? That would be interesting
for performance and energy saving to disable the interrupts until
'cpu0_hot' is reached, no?
--
<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:[~2020-02-24 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 16:54 Ondrej Jirman
2020-02-24 17:06 ` Daniel Lezcano
2020-02-24 17:23 ` Ondřej Jirman
2020-02-24 17:39 ` Ondřej Jirman
2020-02-24 17:56 ` Daniel Lezcano [this message]
2020-02-24 18:33 ` Ondřej Jirman
2020-02-25 9:05 ` Maxime Ripard
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=25a5dfb2-93bb-90c3-8156-0cfbed1f9995@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=megous@megous.com \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®