public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Chen-Yu Tsai <wens@csie.org>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Rafael Wysocki <rjw@rjwysocki.net>,
	"open list:THERMAL" <linux-pm@vger.kernel.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Eduardo Valentin <edubezval@gmail.com>,
	Zhang Rui <rui.zhang@intel.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	devicetree <devicetree@vger.kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 04/10] ARM: dts: sun[4-7]i: Remove "cooling-{min|max}-level" for CPU nodes
Date: Wed, 14 Feb 2018 08:42:52 +0530	[thread overview]
Message-ID: <20180214031252.GW28462@vireshk-i7> (raw)
In-Reply-To: <CAGb2v65Rq5UY_=Fspb_j79a36SK_f+dd2Yb2zAqfg7riiaEO7g@mail.gmail.com>

On 13-02-18, 17:18, Chen-Yu Tsai wrote:
> On Tue, Feb 13, 2018 at 5:13 PM, Maxime Ripard
> <maxime.ripard@bootlin.com> wrote:
> > On Fri, Feb 09, 2018 at 02:28:04PM +0530, Viresh Kumar wrote:
> >> The "cooling-min-level" and "cooling-max-level" properties are not
> >> parsed by any part of the kernel currently and the max cooling state of
> >> a CPU cooling device is found by referring to the cpufreq table instead.
> 
> That doesn't mean that other systems aren't using it.

Are you aware of any systems which are using them ?

> It's still part of
> the device tree binding. Last I checked, while they are optional, they
> aren't deprecated.

Yeah, it isn't deprecated yet. Though the last patches of this series
tries to do something similar.

> Any comments from the device tree maintainers?

None yet.

-- 
viresh

  reply	other threads:[~2018-02-14  3:12 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09  8:58 [PATCH 00/10] thermal: Remove "cooling-{min|max}-level" properties Viresh Kumar
2018-02-09  8:58 ` [PATCH 01/10] ARM: dts: exynos: Remove "cooling-{min|max}-level" for CPU nodes Viresh Kumar
2018-02-13 18:16   ` Krzysztof Kozlowski
2018-02-09  8:58 ` [PATCH 02/10] ARM: dts: omap: " Viresh Kumar
2018-02-12 17:17   ` Tony Lindgren
2018-02-12 17:18     ` Tony Lindgren
2018-02-09  8:58 ` [PATCH 03/10] ARM: dts: mt7623: " Viresh Kumar
2018-02-18 23:26   ` Rob Herring
2018-02-09  8:58 ` [PATCH 04/10] ARM: dts: sun[4-7]i: " Viresh Kumar
2018-02-13  9:13   ` Maxime Ripard
2018-02-13  9:18     ` Chen-Yu Tsai
2018-02-14  3:12       ` Viresh Kumar [this message]
2018-02-09  8:58 ` [PATCH 05/10] ARM64: dts: hi6220: " Viresh Kumar
2018-03-02 16:03   ` Wei Xu
     [not found] ` <cover.1518166039.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2018-02-09  8:58   ` [PATCH 06/10] ARM64: dts: meson: " Viresh Kumar
2018-02-09  9:03     ` Neil Armstrong
2018-03-12  4:32       ` Viresh Kumar
2018-03-20  1:37     ` Viresh Kumar
2018-03-27 12:29       ` Arnd Bergmann
2018-02-09  8:58   ` [PATCH 07/10] ARM: dts: gemini: Remove "cooling-{min|max}-level" for gpio-fan node Viresh Kumar
2018-03-12  4:35     ` Viresh Kumar
2018-03-20  1:43       ` Viresh Kumar
2018-03-20  3:10     ` Linus Walleij
2018-03-27 12:26       ` Arnd Bergmann
2018-03-27 12:29         ` Linus Walleij
2018-02-09  8:58   ` [PATCH 10/10] dt-bindings: thermal: Remove "cooling-{min|max}-level" properties Viresh Kumar
2018-02-18 23:29     ` Rob Herring
2018-02-19  3:43       ` Viresh Kumar
2018-02-19 18:01         ` Rob Herring
2018-03-12  4:38     ` Viresh Kumar
2018-03-20 12:49       ` Zhang Rui
2018-03-27 13:46         ` Eduardo Valentin
2018-02-09  8:58 ` [PATCH 08/10] ARM64: dts: meson: Remove "cooling-{min|max}-level" for gpio-fan node Viresh Kumar
2018-02-09  9:04   ` Neil Armstrong
2018-02-09  8:58 ` [PATCH 09/10] dt-bindings: cpufreq-dt: Remove "cooling-{min|max}-level" properties Viresh Kumar
2018-02-18 23:26   ` Rob Herring

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=20180214031252.GW28462@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=vincent.guittot@linaro.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