From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Lukasz Luba <lukasz.luba@arm.com>,
gao.yunxiao6@gmail.com, rui.zhang@intel.com, amitk@kernel.org,
robh+dt@kernel.org, javi.merino@kernel.org
Cc: linux-pm@vger.kernel.org, kernel-team@android.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
orsonzhai@gmail.com, zhang.lyra@gmail.com,
"jeson.gao" <jeson.gao@unisoc.com>
Subject: Re: [RFC 1/2] dt-bindings: thermal: sprd: Add virtual thermal documentation
Date: Fri, 27 Nov 2020 14:26:07 +0100 [thread overview]
Message-ID: <1af5220c-f598-58f4-488e-fdd505477ed5@linaro.org> (raw)
In-Reply-To: <724ddf78-483c-2cf3-441c-4885af8425a9@arm.com>
Hi Lukasz,
On 27/11/2020 10:27, Lukasz Luba wrote:
>
>
> On 11/27/20 8:35 AM, gao.yunxiao6@gmail.com wrote:
>> From: "jeson.gao" <jeson.gao@unisoc.com>
>>
>> virtual thermal node definition description in dts file
>>
>> Signed-off-by: jeson.gao <jeson.gao@unisoc.com>
>> ---
[ ... ]
> It's coming back. There were attempts to solve this problem.
> Javi tried to solved this using hierarchical thermal zones [1].
> It was even agreed (IIRC during LPC) but couldn't continue. Then Eduardo
> was going to continue this (last message at [3]). Unfortunately,
> development stopped.
>
> I also have out-of-tree similar implementation for my Odroid-xu4,
> which does no have an 'SoC' sensor, but have CPU sensors and needs
> some aggregation function to get temperature.
>
> I can pick up Javi's patches and continue 'hierarchical thermal zones'
> approach.
>
> Javi, Daniel, Rui what do you think?
I already worked on the hierarchical thermal zones and my opinion is
that fits not really well.
We want to define a new feature because the thermal framework is built
on the 1:1 relationship between a governor and a thermal zone.
Practically speaking, we want to mitigate two thermal zones from one
governor, especially here the IPA governor.
The DTPM framework is being implemented to solve that by providing an
automatic power rebalancing between the power manageable capable devices.
In our case, the IPA would stick on the 'sustainable-power' resulting on
the aggregation of the two performance domains and set the power limit
on the parent node. The automatic power rebalancing will ensure maximum
throughput between the two performance domains instead of capping the whole.
--
<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:[~2020-11-27 13:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 8:35 [RFC 1/2] dt-bindings: thermal: sprd: Add virtual thermal documentation gao.yunxiao6
2020-11-27 9:27 ` Lukasz Luba
2020-11-27 13:26 ` Daniel Lezcano [this message]
2020-11-27 13:58 ` Lukasz Luba
2020-11-30 9:03 ` gao yunxiao
2020-11-30 9:40 ` Daniel Lezcano
2020-11-30 10:57 ` gao yunxiao
2020-11-30 17:36 ` 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=1af5220c-f598-58f4-488e-fdd505477ed5@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=amitk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gao.yunxiao6@gmail.com \
--cc=javi.merino@kernel.org \
--cc=jeson.gao@unisoc.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=orsonzhai@gmail.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=zhang.lyra@gmail.com \
/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).