From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
linux-pm@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] thermal/core: Introduce user trip points
Date: Tue, 2 Jul 2024 18:31:52 +0200 [thread overview]
Message-ID: <2a8f5b5f-b67a-4bd0-afe9-f09473aea2d5@linaro.org> (raw)
In-Reply-To: <CAJZ5v0jV+0bWqpCR1Q2rYLJvx0J6hgExzRks6YDPL9gX_HK0rA@mail.gmail.com>
On 02/07/2024 13:03, Rafael J. Wysocki wrote:
[ ... ]
>>> Trips cannot be created on the fly ATM.
>>>
>>> What can be done is to create trips that are invalid to start with and
>>> then set their temperature via sysfs. This has been done already for
>>> quite a while AFAICS.
>>
>> Yes, I remember that.
>>
>> I would like to avoid introducing more weirdness in the thermal
>> framework which deserve a clear ABI.
>>
>> What is missing to create new trip points on the fly ?
>
> A different data structure to store them (essentially, a list instead
> of an array).
>
> I doubt it's worth the hassle.
>
> What's wrong with the current approach mentioned above? It will need
> to be supported going forward anyway.
So when the "user trip point" option will be set, a thermal zone will
have ~ten(?) user trip points initialized to an invalid temperature ?
--
<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-07-02 16:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 8:54 [PATCH] thermal/core: Introduce user trip points Daniel Lezcano
2024-06-28 13:56 ` Rafael J. Wysocki
2024-07-01 13:17 ` Daniel Lezcano
2024-07-01 13:36 ` Rafael J. Wysocki
2024-07-01 15:13 ` Daniel Lezcano
2024-07-01 15:47 ` Rafael J. Wysocki
2024-07-01 15:50 ` Daniel Lezcano
2024-07-01 16:26 ` Rob Herring
2024-07-02 9:29 ` Daniel Lezcano
2024-07-02 10:22 ` Rafael J. Wysocki
2024-07-02 10:56 ` Daniel Lezcano
2024-07-02 11:03 ` Rafael J. Wysocki
2024-07-02 11:17 ` Rafael J. Wysocki
2024-07-02 16:31 ` Daniel Lezcano [this message]
2024-07-02 17:15 ` Rafael J. Wysocki
2024-07-02 22:49 ` Daniel Lezcano
2024-07-03 11:20 ` Rafael J. Wysocki
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=2a8f5b5f-b67a-4bd0-afe9-f09473aea2d5@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.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).