From: Peter Geis <hidden> Date: 2021-07-30 15:17:43
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 <redacted>
---
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(+)
On Fri, 30 Jul 2021 11:17:27 -0400, 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).
Applied, thanks!
[1/1] arm64: dts: rockchip: add thermal fan control to rockpro64
commit: 440f361af90acff36eb3d89c1f03debeab7b3fb8
Best regards,
--
Heiko Stuebner [off-list ref]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Daniel Lezcano <hidden> Date: 2021-08-13 13:00:02
On 30/07/2021 17:17, Peter Geis wrote:
quoted hunk
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 <redacted>
---
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(+)
From: Robin Murphy <robin.murphy@arm.com> Date: 2021-08-13 13:52:06
On 2021-08-13 13:59, Daniel Lezcano wrote:
On 30/07/2021 17:17, Peter Geis wrote:
quoted
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 <redacted>
---
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(+)
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.
From: Daniel Lezcano <hidden> Date: 2021-08-13 14:54:48
Hi Robin,
On 13/08/2021 15:51, Robin Murphy wrote:
On 2021-08-13 13:59, Daniel Lezcano wrote:
quoted
On 30/07/2021 17:17, Peter Geis wrote:
quoted
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 <redacted>
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.
From: Peter Geis <hidden> Date: 2021-08-13 15:14:11
On Fri, Aug 13, 2021 at 10:54 AM Daniel Lezcano
[off-list ref] wrote:
Hi Robin,
On 13/08/2021 15:51, Robin Murphy wrote:
quoted
On 2021-08-13 13:59, Daniel Lezcano wrote:
quoted
On 30/07/2021 17:17, Peter Geis wrote:
quoted
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 <redacted>
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.
That's the same issue I had on the rockpro64.
Thanks for your answer.
What would be the governor for this setup ?
The default governor when using arm64_defconfig is step_wise.
From: Daniel Lezcano <hidden> Date: 2021-08-13 15:46:22
On 13/08/2021 17:10, Peter Geis wrote:
On Fri, Aug 13, 2021 at 10:54 AM Daniel Lezcano
[off-list ref] wrote:
quoted
Hi Robin,
On 13/08/2021 15:51, Robin Murphy wrote:
quoted
On 2021-08-13 13:59, Daniel Lezcano wrote:
quoted
On 30/07/2021 17:17, Peter Geis wrote:
quoted
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 <redacted>
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.
That's the same issue I had on the rockpro64.
quoted
Thanks for your answer.
What would be the governor for this setup ?
The default governor when using arm64_defconfig is step_wise.