From: Rob Herring <robh@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Zhang Rui <rui.zhang@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
daniel.lezcano@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 10/10] dt-bindings: thermal: Remove "cooling-{min|max}-level" properties
Date: Mon, 19 Feb 2018 12:01:24 -0600 [thread overview]
Message-ID: <20180219180124.22rcnjoyvv3qw3cl@rob-hp-laptop> (raw)
In-Reply-To: <20180219034338.GI28462@vireshk-i7>
On Mon, Feb 19, 2018 at 09:13:38AM +0530, Viresh Kumar wrote:
> On 18-02-18, 17:29, Rob Herring wrote:
> > On Fri, Feb 09, 2018 at 02:28:10PM +0530, Viresh Kumar wrote:
> > > The "cooling-min-level" and "cooling-max-level" properties are not
> > > parsed by any part of kernel currently and the max cooling state of a
> > > CPU cooling device is found by referring to the cpufreq table instead.
> >
> > What about non-CPU devices? A fan for example.
>
> Even they aren't using these properties. The gpio-fan binding[1] for
> example uses the "gpio-fan,speed-map" property instead to find the
> number of states it supports.
Okay.
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-02-19 18:01 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
2018-02-09 8:58 ` [PATCH 05/10] ARM64: dts: hi6220: " Viresh Kumar
2018-03-02 16:03 ` Wei Xu
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 08/10] ARM64: dts: meson: " 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
2018-02-09 8:58 ` [PATCH 10/10] dt-bindings: thermal: " Viresh Kumar
2018-02-18 23:29 ` Rob Herring
2018-02-19 3:43 ` Viresh Kumar
2018-02-19 18:01 ` Rob Herring [this message]
2018-03-12 4:38 ` Viresh Kumar
2018-03-20 12:49 ` Zhang Rui
2018-03-27 13:46 ` Eduardo Valentin
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=20180219180124.22rcnjoyvv3qw3cl@rob-hp-laptop \
--to=robh@kernel.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=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).