From: Robin Murphy <robin.murphy@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Peter Geis <pgwipeout@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] arm64: dts: rockchip: add thermal fan control to rockpro64
Date: Fri, 13 Aug 2021 14:51:54 +0100 [thread overview]
Message-ID: <893701da-ea17-00ab-5e31-c745051ac9b9@arm.com> (raw)
In-Reply-To: <ad6d8025-977c-9ff2-81ff-a417df48231c@linaro.org>
On 2021-08-13 13:59, Daniel Lezcano wrote:
> On 30/07/2021 17:17, Peter Geis wrote:
>> The rockpro64 had a fan node since
>> commit 5882d65c1691 ("arm64: dts: rockchip: Add PWM fan for RockPro64")
>> however it was never tied into the thermal driver for automatic control.
>>
>> Add the links to the thermal node to permit the kernel to handle this
>> automatically.
>> Borrowed from the (rk3399-khadas-edge.dtsi).
>>
>> Signed-off-by: Peter Geis <pgwipeout@gmail.com>
>> ---
>>
>> Changelog:
>> v3:
>> Removed the gpu nodes to prevent in-fighting (thanks Robin!)
>>
>> v2:
>> Adjusted fan setpoints for less noise
>>
>> .../boot/dts/rockchip/rk3399-rockpro64.dtsi | 29 +++++++++++++++++++
>> 1 file changed, 29 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi
>> index 6bff8db7d33e..83db4ca67334 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi
>> +++ b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi
>> @@ -69,6 +69,7 @@ diy_led: led-1 {
>>
>> fan: pwm-fan {
>> compatible = "pwm-fan";
>> + cooling-levels = <0 100 150 200 255>;
>> #cooling-cells = <2>;
>> fan-supply = <&vcc12v_dcin>;
>> pwms = <&pwm1 0 50000 0>;
>> @@ -245,6 +246,34 @@ &cpu_b1 {
>> cpu-supply = <&vdd_cpu_b>;
>> };
>>
>> +&cpu_thermal {
>> + trips {
>> + cpu_warm: cpu_warm {
>> + temperature = <55000>;
>> + hysteresis = <2000>;
>> + type = "active";
>> + };
>> +
>> + cpu_hot: cpu_hot {
>> + temperature = <65000>;
>> + hysteresis = <2000>;
>> + type = "active";
>> + };
>> + };
>> +
>
> Why two trip points ?
>
> Why not one functioning temperature and no lower / upper limits for the
> cooling maps ?
Certainly when I first did this for NanoPC-T4, IIRC it was to avoid the
fan ramping up too eagerly, since level 1 for my fan is effectively
silent but still cools enough to let a moderate load eventually settle
to a steady state below the second trip.
Robin.
>> + cooling-maps {
>> + map2 {
>> + trip = <&cpu_warm>;
>> + cooling-device = <&fan THERMAL_NO_LIMIT 1>;
>> + };
>> +
>> + map3 {
>> + trip = <&cpu_hot>;
>> + cooling-device = <&fan 2 THERMAL_NO_LIMIT>;
>> + };
>> + };
>> +};
>> +
>> &emmc_phy {
>> status = "okay";
>> };
>>
>
>
next prev parent reply other threads:[~2021-08-13 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 15:17 Peter Geis
2021-08-13 8:51 ` Heiko Stuebner
2021-08-13 12:59 ` Daniel Lezcano
2021-08-13 13:51 ` Robin Murphy [this message]
2021-08-13 14:54 ` Daniel Lezcano
2021-08-13 15:10 ` Peter Geis
2021-08-13 15:46 ` Daniel Lezcano
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=893701da-ea17-00ab-5e31-c745051ac9b9@arm.com \
--to=robin.murphy@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®