[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180219034338.GI28462@vireshk-i7>
Date: Mon, 19 Feb 2018 09:13:38 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Rob Herring <robh@...nel.org>
Cc: Rafael Wysocki <rjw@...ysocki.net>,
Zhang Rui <rui.zhang@...el.com>,
Eduardo Valentin <edubezval@...il.com>,
linux-pm@...r.kernel.org,
Vincent Guittot <vincent.guittot@...aro.org>,
Mark Rutland <mark.rutland@....com>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
daniel.lezcano@...aro.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 10/10] dt-bindings: thermal: Remove
"cooling-{min|max}-level" properties
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.
--
viresh
[1] Documentation/devicetree/bindings/gpio/gpio-fan.txt
Powered by blists - more mailing lists