mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ondřej Jirman" <megous@megous.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: 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:23:28 +0100	[thread overview]
Message-ID: <20200224172328.yauwfgov664ayrd6@core.my.home> (raw)
In-Reply-To: <2e4213a6-2aaf-641c-f741-9503f3ffd5fe@linaro.org>

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 {
> > +				cpu0_hot: 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.

> >  			polling-delay = <0>;
> >  			thermal-sensors = <&ths 1>;
> > +
> > +			trips {
> > +				cpu1_hot: cpu-hot {
> > +					temperature = <80000>;
> > +					hysteresis = <2000>;
> > +					type = "passive";
> 
> I'm curious, can you really reach this temperature with a cortex-a7
> running at 1.2GHz max?

That depends on ambient temperature. I'd say easily. My A83T is running
iniside enclosed space with no cooling other than dissipating heat to
the board.

Anyway, I'm running my A83T boards at 1.8GHz. And A83T can run up to 2GHz
at the best SoC bin.

I'll probably submit updated cpufreq table at some point too, once I fix
it up to use the SoC bin information.

https://megous.com/git/linux/commit/?h=ths-5.6&id=171b7c3c3db98b5939d28d0c96b384edda95cec3

regards,
	o.

> > +				};
> > +
> > +				cpu1_very_hot: cpu-very-hot {
> > +					temperature = <100000>;
> > +					hysteresis = <0>;
> > +					type = "critical";
> > +				};
> > +			};
> > +
> > +			cooling-maps {
> > +				cpu-hot-limit {
> > +					trip = <&cpu1_hot>;
> > +					cooling-device = <&cpu100 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
> > +							 <&cpu101 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
> > +							 <&cpu102 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
> > +							 <&cpu103 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
> > +				};
> > +			};
> >  		};
> >  
> >  		gpu_thermal: gpu-thermal {
> > 
> 
> 
> -- 
>  <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
> 

  reply	other threads:[~2020-02-24 17:23 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 [this message]
2020-02-24 17:39     ` Ondřej Jirman
2020-02-24 17:56       ` Daniel Lezcano
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=20200224172328.yauwfgov664ayrd6@core.my.home \
    --to=megous@megous.com \
    --cc=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=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®