[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18ade2d0-ebda-0526-71f3-65a0b2685068@linexp.org>
Date: Sun, 24 Jul 2022 20:27:54 +0200
From: Daniel Lezcano <daniel.lezcano@...exp.org>
To: Niklas Söderlund <niklas.soderlund@...natech.se>
Cc: daniel.lezcano@...aro.org, rafael@...nel.org, rui.zhang@...el.com,
khilman@...libre.com, abailon@...libre.com, amitk@...nel.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
"open list:RENESAS R-CAR THERMAL DRIVERS"
<linux-renesas-soc@...r.kernel.org>
Subject: Re: [PATCH v1 17/33] thermal/drivers/rcar: Switch to new of API
Hi Niklas,
I tried to reproduce the issue but without success.
What sensor are you using ?
On 19/07/2022 11:10, Niklas Söderlund wrote:
> Hi Daniel,
>
> Thanks for your work.
>
> On 2022-07-10 23:24:07 +0200, Daniel Lezcano wrote:
>> The thermal OF code has a new API allowing to migrate the OF
>> initialization to a simpler approach.
>>
>> Use this new API.
> I tested this together with the series it depends on and while
> temperature monitoring seems to work fine it breaks the emul_temp
> interface (/sys/class/thermal/thermal_zone2/emul_temp).
>
> Before this change I can write a temperature to this file and have it
> trigger actions, in my test-case changing the cooling state, which I
> observe in /sys/class/thermal/cooling_device0/cur_state.
>
> Likewise before this change I could trip the critical trip-point that
> would power off the board using the emul_temp interface, this too no
> longer works,
>
> echo 120000 > /sys/class/thermal/thermal_zone2/emul_temp
>
> Is this an intention change of the new API?
Powered by blists - more mailing lists