Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] arm64: dts: amlogic: Add missing cooling device properties for CPUs
Date: Mon, 28 May 2018 16:43:58 +0530	[thread overview]
Message-ID: <20180528111358.meyle364fy6wuruf@vireshk-i7> (raw)
In-Reply-To: <20180525211025.c73zdcdtyuvlewng@localhost>

On 25-05-18, 14:10, Olof Johansson wrote:
> On Fri, May 25, 2018 at 11:10:01AM +0530, Viresh Kumar wrote:
> > The cooling device properties, like "#cooling-cells" and
> > "dynamic-power-coefficient", should either be present for all the CPUs
> > of a cluster or none. If these are present only for a subset of CPUs of
> > a cluster then things will start falling apart as soon as the CPUs are
> > brought online in a different order. For example, this will happen
> > because the operating system looks for such properties in the CPU node
> > it is trying to bring up, so that it can register a cooling device.
> > 
> > Add such missing properties.
> 
> This seems awkward compared to just having one cooling-cells in the /cpus node
> instead.

Well, we don't allow that property to be present in /cpus node right
now and it is per device. And then we may not want all the CPUs to be
cooling devices really.

> What's it used for? I don't see any properties in the device nodes on meson-gxm
> that have any cooling-foo cells in them? So why should #cooling-cells be
> needed?

This property is required to declare a device as a cooling-device and
the device here is CPU. We use it as a cooling device by limiting its
higher range of frequencies, so that it doesn't generate too much
heat.

It is already there for CPU0 and CPU4, but it should really be there
for all the CPUs, like we have clock, supply, caches, etc.

-- 
viresh

  parent reply	other threads:[~2018-05-28 11:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25  5:40 [PATCH 0/6] arm64: dts: Add missing cooling device properties for CPUs Viresh Kumar
2018-05-25  5:40 ` [PATCH 1/6] arm64: dts: amlogic: " Viresh Kumar
2018-05-25 21:10   ` Olof Johansson
2018-05-26  8:37     ` Neil Armstrong
2018-05-28 11:16       ` Viresh Kumar
2018-05-28 11:13     ` Viresh Kumar [this message]
2018-06-02  8:14       ` Olof Johansson
2018-06-05  4:37         ` Viresh Kumar
2018-05-25  5:40 ` [PATCH 2/6] arm64: dts: freescale: " Viresh Kumar
2018-07-03  7:34   ` Shawn Guo
2018-07-03  8:34     ` Viresh Kumar
2018-07-03 10:08       ` Shawn Guo
2018-05-25  5:40 ` [PATCH 3/6] arm64: dts: hisilicon: " Viresh Kumar
2018-05-26 18:00   ` Wei Xu
2018-05-26 18:21     ` Wei Xu
2018-07-18  5:58       ` Viresh Kumar
2018-07-18 15:32   ` Wei Xu
2018-05-25  5:40 ` [PATCH 4/6] arm64: dts: mediatek: " Viresh Kumar
2018-07-02 16:56   ` Matthias Brugger
2018-05-25  5:40 ` [PATCH 5/6] arm64: dts: rockchip: " Viresh Kumar
2018-06-15 11:23   ` Heiko Stübner
2018-05-25  5:40 ` [PATCH 6/6] arm64: dts: socionext: " Viresh Kumar
2018-06-01  3:25   ` Masahiro Yamada
2018-06-04  7:14     ` Viresh Kumar

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=20180528111358.meyle364fy6wuruf@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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