mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Anand Moon <linux.amoon@gmail.com>
Cc: Willy Wolff <willy.mh.wolff@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	Kukjin Kim <kgene@kernel.org>,
	Javier Martinez Canillas <javier@osg.samsung.com>,
	devicetree <devicetree@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	"linux-samsung-soc@vger.kernel.org" 
	<linux-samsung-soc@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: exynos: Exynos5422 Odroid-XU* incomplete thermal-zones definition
Date: Sun, 25 Jun 2017 19:19:21 +0200	[thread overview]
Message-ID: <20170625171921.sijfwgnuk5cwdi74@kozik-lap> (raw)
In-Reply-To: <CANAwSgSZyhf-7BjwqoSAxBg=UDzCwEG=thpASEmZ=p=N5gpFQw@mail.gmail.com>

On Sun, Jun 25, 2017 at 10:25:32PM +0530, Anand Moon wrote:
> Hi Krzysztof
> 
> On 25 June 2017 at 20:59, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> > On Sun, Jun 25, 2017 at 08:48:13PM +0530, Anand Moon wrote:
> >> Hi Krzystof,
> >> >> 2: We should also increase the tips from 4 to 8 to support different
> >> >> cluster of cpu's.
> >> >
> >> > There are 4 CPU thermal zones on Exynos5422. What do you want to expand?
> >>
> >> What I meant was to support more trip point to address below.
> >> [    2.776320] exynos-tmu 100a0000.tmu: More trip points than
> >> supported by this TMU.
> >> [    2.782370] exynos-tmu 100a0000.tmu: 2 trip points should be
> >> configured in polling mode.
> >>
> >
> > I do not understand what you want to achieve. I added 2 trip points in
> > polling mode for the CPU cooling mode. Just describe the problem and
> > send the patch - it is the best way to explain one's thought...
> >
> >> >> 3: To avoid duplication of cooling-maps we can make tmu sensor work
> >> >> differently for cluster of cpu's
> >> >>       tmu_cpu0: handle pwm-fan control.
> >> >>       tmu_cpu1: handle cpu[0-3] cpufreq mapping.
> >> >>       tmu_cpu2: handle cpu[4-7] cpufreq mapping.
> >> >
> >> > I miss the point behind this. Why fan should work only when CPU4
> >> > (tmu_cpu0) is heated and not CPU5-7 (rest of cpu tmu's)?
> >>
> >> Ok fan should work on all the thermal zone. To avoid thermal shutdown.
> >>
> >> But I want to avoid scaling down of all the cores of cpu to low freq
> >> as cooling-maps cross the alert temperature. For below example.
> >> ----
> >>  map3 {
> >>               trip = <&cpu1_alert3>;
> >>               cooling-device = <&cpu0 0 2>;
> >>  };
> >>  map4 {
> >>               trip = <&cpu1_alert3>;
> >>               cooling-device = <&cpu4 0 2>;
> >>  };
> >>
> >>  map5 {
> >>               trip = <&cpu1_alert4>;
> >>               cooling-device = <&cpu0 3 7>;
> >>  };
> >>  map6 {
> >>              trip = <&cpu1_alert4>;
> >>              cooling-device = <&cpu4 3 12>;
> >>  };
> >>
> >> What I want to configure thermal zone as.
> >>
> >> cpu0_thermal: cpu0-thermal {
> >>      configure cluster of cpu[0-3]
> >>      {
> >>         tips
> >>      }
> >>      cooling map
> >>      {
> >>          device handle cpu[0-3] with frequency scaling at particular
> >> alert temperature.
> >>      }
> >> }
> >
> > cpu0_thermal is attached to tmu_cpu0 which is the temperature of CPU4
> > (first big core). I do not see reason behind connecting thermal zone
> > (thus temperature) of CPU4 with frequency of LITTLE cluster (CPU0-3). In
> > case of busy CPU4, you will scale down CPU0-3. Does not make sense.
> >
> 
> Both the cpu cluster are independent and have different cpu-freqency scaling.
> that is the reason to for my changes.

Still does not make sense. Big is busy, LITTLE is doing nothing and you
want to scale down LITTLE. No reason.

> 
> >> cpu1_thermal: cpu1-thermal {
> >>      configure cluster of cpu[4-7]
> >>      {
> >>         tips
> >>      }
> >>      cooling map
> >>      {
> >>          device handle cpu[4-7] with frequency scaling at particular
> >> alert temperature.
> >>      }
> >> }
> >>
> >> We can chose to configure rest of the thermal-zone on this approach.
> >> Please share your thoughts.
> >
> > I am sorry, I do not understand the idea, the problem nor the solution.
> >
> > Best regards,
> > Krzysztof
> >
> 
> Sorry for not able to express my self in technical terms.
> my changes are based on exynos5433-tmu at this moment.
> Just attaching small patch to share my point.

On Odroid XU3-family, all TMU interrupt-driven configureable trip points
are configured. Why are you referring to Exynos5433?

Best regards,
Krzysztof

  reply	other threads:[~2017-06-25 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 21:09 Willy Wolff
2017-06-25  7:57 ` Krzysztof Kozlowski
2017-06-25 13:23 ` Anand Moon
2017-06-25 13:31   ` Krzysztof Kozlowski
2017-06-25 15:18     ` Anand Moon
2017-06-25 15:29       ` Krzysztof Kozlowski
2017-06-25 16:55         ` Anand Moon
2017-06-25 17:19           ` Krzysztof Kozlowski [this message]
2017-06-25 17:59             ` Anand Moon

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=20170625171921.sijfwgnuk5cwdi74@kozik-lap \
    --to=krzk@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=javier@osg.samsung.com \
    --cc=kgene@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux.amoon@gmail.com \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=willy.mh.wolff@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 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®