linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Zhang Rui <rui.zhang@intel.com>,
	Eduardo Valentin <edubezval@gmail.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	linux-pm@vger.kernel.org, robh+dt@kernel.org,
	devicetree@vger.kernel.org, Punit.Agrawal@arm.com,
	ionela.voinescu@arm.com
Subject: Re: [Query] thermal: Who is using "cooling-{min|max}-level}" properties ?
Date: Wed, 7 Feb 2018 11:45:31 +0100	[thread overview]
Message-ID: <11fbba25-7029-8a13-476e-ea2f2de6fbf9@linaro.org> (raw)
In-Reply-To: <20180207102446.GS28462@vireshk-i7>

On 07/02/2018 11:24, Viresh Kumar wrote:
> On 07-02-18, 11:04, Daniel Lezcano wrote:
>> Yeah, this is a bit fuzzy. There are still cooling-{min|max}-*state*
>> definitions in the DTs
>>
>> Documentation/devicetree/bindings/hwmon/pwm-fan.txt:
>> cooling-min-state = <0>;
>> arch/arm/boot/dts/exynos4412-odroidu3.dts:
>> cooling-min-state = <0>;
>> arch/arm/boot/dts/exynos5410-odroidxu.dts:
>> cooling-min-state = <0>;
>> arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi:
>> cooling-min-state = <0>;
>> arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi:
>> cooling-min-state = <0>;
>>
>>
>> IIUC, the cooling-device in the mapping defines the min and max states
>> which are the values used in the thermal zone binding.
>>
>> And the cooling-[min|max]-level are the hardware limits:
>>
>> cooling-min-level <= cooling-device min|max state <= cooling-max-level
>>
>> For example on the hikey6220:
>>
>> The DT specifies for CPU0:
>>
>> 	operating-points-v2 = <&cpu_opp_table>;
>> 	cooling-min-level = <4>;
>> 	cooling-max-level = <0>;
>> 	#cooling-cells = <2>; /* min followed by max */
>>
>> and for the cooling device for map0
>>
>> 	cooling-device = <&cpu0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
>>
>> So if my understanding is correct, the optional property
>> cooling-[min|max]-level is used to make sure the cooling device min
>> state and max state are in the hardware boundaries. And the thermal
>> framework misses to do the consistency check at init.
>>
>> I'm not sure how useful are cooling-{min|max}-*state* bindings.

I meant here cooling-{min|max}-*level*

> Okay, but we aren't validating it this way in code. Isn't it ?

Yes, that is my understanding. cooling-min-level and cooling-max-level
are not used in the thermal framework code today.

So if they are defined, we should check the cooling-device max and min
are in the boundaries (if they are different from no-limit).

That needs confirmation from the maintainers, I'm not 100% sure.


-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  reply	other threads:[~2018-02-07 10:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07  6:59 [Query] thermal: Who is using "cooling-{min|max}-level}" properties ? Viresh Kumar
2018-02-07 10:04 ` Daniel Lezcano
     [not found]   ` <c7bd6ed5-b93e-3a07-b4a2-4c3b1eef5fac-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2018-02-07 10:24     ` Viresh Kumar
2018-02-07 10:45       ` Daniel Lezcano [this message]
2018-02-09  6:42         ` Viresh Kumar
2018-02-09  9:15           ` Daniel Lezcano
     [not found]             ` <539699c7-9509-dea2-2b31-c5f6749c99c4-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2018-02-09  9:24               ` Viresh Kumar
2018-02-09 12:14                 ` Daniel Lezcano
     [not found]                   ` <5722441d-c8be-4d29-fab7-28b4e5716961-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2018-02-12  6:10                     ` Viresh Kumar
2018-02-12  8:39                       ` Daniel Lezcano
2018-02-12  8:52                         ` Viresh Kumar
2018-02-12  9:52                           ` Daniel Lezcano
2018-02-12 10:17                             ` 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=11fbba25-7029-8a13-476e-ea2f2de6fbf9@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=Punit.Agrawal@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=ionela.voinescu@arm.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --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).