From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Nicolas Pitre <nico@fluxnic.net>,
"Rafael J . Wysocki" <rafael@kernel.org>,
linux-pm@vger.kernel.org, linux-mediatek@lists.infradead.org,
devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Alexandre Bailon <abailon@baylibre.com>
Subject: Re: [PATCH 0/5] thermal: multi-sensor aggregation support
Date: Thu, 28 Nov 2024 18:38:12 +0100 [thread overview]
Message-ID: <c1c14ada-c0bf-4353-a8ba-7b3a2fb6d971@linaro.org> (raw)
In-Reply-To: <s120q967-4r69-pps2-1qo3-9952r9173125@syhkavp.arg>
Hi Nicolas,
On 27/11/2024 23:05, Nicolas Pitre wrote:
> Gentle ping, feedback appreciated.
I'm currently reviewing the series.
We have been discussing this feature since a long time and multiple
times at different plumbers without any progress since then. So thank
you for proposing an implementation of this feature.
I have some concerns regarding the approach I will raise tomorrow.
Thanks
-- Daniel
> On Tue, 12 Nov 2024, Nicolas Pitre wrote:
>
>> This series provides support for thermal aggregation of multiple sensors.
>> The "one sensor per zone" model is preserved for all its advantages.
>> Aggregation is performed via the creation of a special zone whose purpose
>> consists in aggregating its associated primary zones using a weighted
>> average.
>>
>> Motivation for this work stems from use cases where multiple sensors are
>> contained within the same performance domain. In such case it is preferable
>> to apply thermal mitigation while considering all such sensors as a whole.
>>
>> Previous incarnation by Alexandre Bailon can be found here:
>> https://patchwork.kernel.org/project/linux-pm/cover/20240613132410.161663-1-abailon@baylibre.com/
>>
>> diffstat:
>> .../bindings/thermal/thermal-zones.yaml | 5 +-
>> arch/arm64/boot/dts/mediatek/mt8195.dtsi | 210 +-----
>> drivers/thermal/Kconfig | 27 +
>> drivers/thermal/thermal_core.c | 643 ++++++++++++++++++
>> drivers/thermal/thermal_core.h | 14 +
>> drivers/thermal/thermal_of.c | 86 ++-
>> 6 files changed, 780 insertions(+), 205 deletions(-)
>>
--
<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:[~2024-11-28 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 5:19 [PATCH 0/5] thermal: multi-sensor aggregation support Nicolas Pitre
2024-11-12 5:19 ` [PATCH 1/5] thermal: of: properly parse coefficients with multiple thermal-sensors entries Nicolas Pitre
2024-11-12 5:19 ` [PATCH 2/5] dt-bindings: thermal: Restore the thermal-sensors property Nicolas Pitre
2024-11-12 5:19 ` [PATCH 3/5] thermal: aggregation support Nicolas Pitre
2024-11-12 5:19 ` [PATCH 4/5] thermal: automatic " Nicolas Pitre
2024-11-12 5:19 ` [PATCH 5/5] ARM64: mt8195: Use thermal aggregation for big and little cpu Nicolas Pitre
2024-11-27 22:05 ` [PATCH 0/5] thermal: multi-sensor aggregation support Nicolas Pitre
2024-11-28 17:38 ` Daniel Lezcano [this message]
2024-11-29 20:00 ` Daniel Lezcano
2024-12-02 3:41 ` Chen-Yu Tsai
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=c1c14ada-c0bf-4353-a8ba-7b3a2fb6d971@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=abailon@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=rafael@kernel.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