diff options
author | Diederik de Haas <didi.debian@cknow.org> | 2024-07-04 22:18:33 +0300 |
---|---|---|
committer | Heiko Stuebner <heiko@sntech.de> | 2024-07-08 17:25:35 +0300 |
commit | dbdadc14b94e1c0326a430c1f84592a9b5c6b6d2 (patch) | |
tree | 9730af3c95714f540660b5daeb08bf2ac487c2fb /tools/perf/scripts/python/task-analyzer.py | |
parent | e261bd74000ca80e5483ba8a8bda509de8cbe7fd (diff) | |
download | linux-dbdadc14b94e1c0326a430c1f84592a9b5c6b6d2.tar.xz |
arm64: dts: rockchip: Add avdd supplies to hdmi on rock64
Pine64's Rock64 was missing the avdd supply properties on the hdmi node,
causing the following warnings:
dwhdmi-rockchip ff3c0000.hdmi: supply avdd-0v9 not found, using dummy regulator
dwhdmi-rockchip ff3c0000.hdmi: supply avdd-1v8 not found, using dummy regulator
In the Rock64 Schematic document version 2.0 those supplies are marked
as DVIDEO_AVDD_1V0 and DVIDEO_AVDD_1V8 respectively, but in version 3.0
those are named HDMI_AVDD_1V0 and HDMI_AVDD_1V8, which is a bit clearer.
In both versions those are connected to LDO3 and LDO1 respectively.
While the DeviceTree property is named 'avdd-0v9-supply' the
'rockchip,dw-hdmi.yaml' binding document notes the following:
A 0.9V supply that powers up the SoC internal circuitry. The actual
pin name varies between the different SoCs and is usually
HDMI_TX_AVDD_0V9 or sometimes HDMI_AVDD_1V0.
So the 'vdd_10' reference is not an error.
Signed-off-by: Diederik de Haas <didi.debian@cknow.org>
Reviewed-by: Dragan Simic <dsimic@manjaro.org>
Link: https://lore.kernel.org/r/20240704191919.38856-1-didi.debian@cknow.org
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions