All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Simon Horman <horms@verge.net.au>
Cc: Yoshihiro Kaneko <ykaneko0929@gmail.com>,
	linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH/RFT] arm64: dts: renesas: r8a7795: Create thermal zone to support IPA
Date: Thu, 11 Apr 2019 18:47:25 +0200	[thread overview]
Message-ID: <20190411164725.GE30887@bigcity.dyn.berto.se> (raw)
In-Reply-To: <20190408122941.wziujh5ibgwy5cdp@verge.net.au>

Hi Simon,

On 2019-04-08 14:29:41 +0200, Simon Horman wrote:
> > > @@ -3172,11 +3158,15 @@
> > >  
> > >  			cooling-maps {
> > >  				map0 {
> > > -					trip = <&sensor3_passive>;
> > > -					cooling-device = <&a57_0 4 4>,
> > > -							 <&a57_1 4 4>,
> > > -							 <&a57_2 4 4>,
> > > -							 <&a57_3 4 4>;
> > > +					trip = <&target>;
> > > +					cooling-device = <&a57_0 0 2>;
> > 
> > We have 5 (0-4) cooling states for the A57s on this SoC. Out of 
> > curiosity why allow states 0-2 here and not force it do more cooling or 
> > keep the to max cooling (4) as before this change as this is set to a 
> > trip point with a rather large temperature? Not saying this is wrong 
> > only curious :-)
> 
> This I do not know. Do you think it would be worth following-up on
> internally?

I'm no expert on this but I think it could be educational to learn why 
not the full range is used. Still this might be correct so I don't want 
to block this patch based on my ignorance.

-- 
Regards,
Niklas Söderlund

WARNING: multiple messages have this Message-ID (diff)
From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Simon Horman <horms@verge.net.au>
Cc: linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Yoshihiro Kaneko <ykaneko0929@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH/RFT] arm64: dts: renesas: r8a7795: Create thermal zone to support IPA
Date: Thu, 11 Apr 2019 18:47:25 +0200	[thread overview]
Message-ID: <20190411164725.GE30887@bigcity.dyn.berto.se> (raw)
In-Reply-To: <20190408122941.wziujh5ibgwy5cdp@verge.net.au>

Hi Simon,

On 2019-04-08 14:29:41 +0200, Simon Horman wrote:
> > > @@ -3172,11 +3158,15 @@
> > >  
> > >  			cooling-maps {
> > >  				map0 {
> > > -					trip = <&sensor3_passive>;
> > > -					cooling-device = <&a57_0 4 4>,
> > > -							 <&a57_1 4 4>,
> > > -							 <&a57_2 4 4>,
> > > -							 <&a57_3 4 4>;
> > > +					trip = <&target>;
> > > +					cooling-device = <&a57_0 0 2>;
> > 
> > We have 5 (0-4) cooling states for the A57s on this SoC. Out of 
> > curiosity why allow states 0-2 here and not force it do more cooling or 
> > keep the to max cooling (4) as before this change as this is set to a 
> > trip point with a rather large temperature? Not saying this is wrong 
> > only curious :-)
> 
> This I do not know. Do you think it would be worth following-up on
> internally?

I'm no expert on this but I think it could be educational to learn why 
not the full range is used. Still this might be correct so I don't want 
to block this patch based on my ignorance.

-- 
Regards,
Niklas Söderlund

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-04-11 16:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 20:49 [PATCH/RFT] arm64: dts: renesas: r8a7795: Create thermal zone to support IPA Yoshihiro Kaneko
2018-12-20 20:49 ` Yoshihiro Kaneko
2018-12-20 20:49 ` [PATCH/RFT] arm64: dts: renesas: r8a7796: " Yoshihiro Kaneko
2018-12-20 20:49   ` Yoshihiro Kaneko
2018-12-20 20:49 ` [PATCH/RFT] arm64: dts: renesas: r8a77965: " Yoshihiro Kaneko
2018-12-20 20:49   ` Yoshihiro Kaneko
2018-12-20 20:49 ` [PATCH/RFT] arm64: dts: renesas: r8a77990: " Yoshihiro Kaneko
2018-12-20 20:49   ` Yoshihiro Kaneko
2019-01-10 16:33 ` [PATCH/RFT] arm64: dts: renesas: r8a7795: " Niklas Söderlund
2019-01-10 16:33   ` Niklas Söderlund
2019-04-08 12:29   ` Simon Horman
2019-04-08 12:29     ` Simon Horman
2019-04-11 16:47     ` Niklas Söderlund [this message]
2019-04-11 16:47       ` Niklas Söderlund
2019-04-24  7:17     ` Geert Uytterhoeven
2019-04-24  7:17       ` Geert Uytterhoeven

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=20190411164725.GE30887@bigcity.dyn.berto.se \
    --to=niklas.soderlund@ragnatech.se \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=ykaneko0929@gmail.com \
    /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 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.