[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2a8f5b5f-b67a-4bd0-afe9-f09473aea2d5@linaro.org>
Date: Tue, 2 Jul 2024 18:31:52 +0200
From: Daniel Lezcano <daniel.lezcano@...aro.org>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Rob Herring <robh@...nel.org>, linux-pm@...r.kernel.org,
Zhang Rui <rui.zhang@...el.com>, Lukasz Luba <lukasz.luba@....com>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] thermal/core: Introduce user trip points
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
Powered by blists - more mailing lists