[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1ef26db5-6e2b-ce27-f9ad-34ff8f4055cb@linaro.org>
Date: Tue, 9 Aug 2022 23:45:46 +0200
From: Daniel Lezcano <daniel.lezcano@...aro.org>
To: Peter Kästle <peter@...e.net>, rafael@...nel.org
Cc: rui.zhang@...el.com, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, Hans de Goede <hdegoede@...hat.com>,
Mark Gross <markgross@...nel.org>,
"open list:ACER ASPIRE ONE TEMPERATURE AND FAN DRIVER"
<platform-driver-x86@...r.kernel.org>
Subject: Re: [PATCH v1 23/26] thermal/drivers/acerhdf: Use generic
thermal_zone_get_trip() function
On 08/08/2022 21:34, Peter Kästle wrote:
> Hello,
>
> some comments. Please merge if those are considered. Thanks.
>
>
> On 05.08.22 16:57, Daniel Lezcano wrote:
>> The thermal framework gives the possibility to register the trip
>> points with the thermal zone. When that is done, no get_trip_* ops are
>> needed and they can be removed.
>>
>> Convert ops content logic into generic trip points and register them
>> with the
>> thermal zone.
>>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@...aro.org>
>
> Acked-by: Peter Kästle <peter@...e.net>
Thanks for reviewing the patch
[ ... ]
>> if (kernelmode && prev_interval != interval) {
>> if (interval > ACERHDF_MAX_INTERVAL) {
>> pr_err("interval too high, set to %d\n",
>
> I don't know the current behavior of the thermal layer well enough.
> Is it ensured, that those new trips[0].temperature / trips[0].hysteresis
> values are taken into account?
I don't have this platform so it is hard to test. All the device tree
based sensors are using now those generic trip points and that works.
--
<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