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: Mon, 12 Feb 2018 09:39:34 +0100 [thread overview]
Message-ID: <0b73e1aa-a88f-fe4b-b33a-0f589000e148@linaro.org> (raw)
In-Reply-To: <20180212061015.GO28462@vireshk-i7>
On 12/02/2018 07:10, Viresh Kumar wrote:
> On 09-02-18, 13:14, Daniel Lezcano wrote:
>> Right. The semantic is unclear. The expected cooling-cells value is
>> always 2 (the code ignore values greater than two and yell if it is less
>> than 2). And the cooling-device binding tells there are two states.
>
> They are fixed to 2 as we don't need to use it differently for now.
> But that's more about how Linux is using this stuff. The binding still
> needs to provide a way to have more cells than just 2.
>
>> So the question is why do we need a cooling-cells as the information is
>> pointless here (always 2) ?
>
> To show that the device is a "cooling-device" and I see that
> consistent with everything else in DT, for example: interrupt-cells,
> gpio-cells, clock-cells, reset-cells, dma-cells. The "*-cells"
> properties is used widely to tell what the device can behave as, i.e.
> a cooling-device in our case.
Ah, yes. That's right.
Well I don't know. If that is the way the other drivers are doing, I
suppose we should keep it as it is.
> Now we always use 2 parameters exactly is a different thing all
> together :)
>
>> I see this field is artificially used to tell the cpufreq driver "please
>> register me as a cooling device". This is inconsistent from my pov.
>
> But that's how its used for every other controller, what's different
> here ?
>
>> Furthermore, the thermal-zone with the cooling device binds with the CPU
>> phandle, not the cooling-cells.
>
> Yeah, because that's the device really.
>
>> Putting apart the device binding changes discussion for the moment. Why
>> not register the cpufreq driver in all the cases and then drop
>
> s/cpufreq driver/cpufreq cooling driver/ ??
yes.
>> cooling-cells ? So when the opps are present, its registers in the
>> cpufreq->ready callback.
>
> How will someone tell if they don't need the cooling infrastructure ?
> Specially for multiplatform thing.
They don't define a cooling device in the DT ?
--
<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
next prev parent reply other threads:[~2018-02-12 8:39 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
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 [this message]
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=0b73e1aa-a88f-fe4b-b33a-0f589000e148@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).