From: Dragan Simic <dsimic@manjaro.org>
To: Diederik de Haas <didi.debian@cknow.org>
Cc: Heiko Stuebner <heiko@sntech.de>, Alex Bee <knaerzche@gmail.com>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: Add avdd supplies to hdmi on rock64
Date: Sun, 07 Jul 2024 23:23:30 +0200 [thread overview]
Message-ID: <31a86ec073e1de9e0241845f8783cd6b@manjaro.org> (raw)
In-Reply-To: <20240704191919.38856-1-didi.debian@cknow.org>
Hello Diederik,
Please see some comments below.
On 2024-07-04 21:18, Diederik de Haas wrote:
> 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>
Already verified the above-quoted statement from the .yaml binding
in the RK3328 and RK3399 datasheets. Thus, hoping that you agree
with the first line:
Helped-by: Dragan Simic <dsimic@manjaro.org>
Reviewed-by: Dragan Simic <dsimic@manjaro.org>
I'd also suggest that a brief comment is added to rk3328-rock64.dts,
right above the "avdd-0v9-supply = <&vdd_10>;" line. Perhaps something
like this:
> + /*
> + * RK3328 requires 1.0 V on HDMI_AVDD_1V0, which is HDMI_AVDD_0V9
> + * and requires 0.9 V on other Rockchip SoCs
> + */
> ---
> arch/arm64/boot/dts/rockchip/rk3328-rock64.dts | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
> b/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
> index 229fe9da9c2d..90fef766f3ae 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
> @@ -154,6 +154,8 @@ &gmac2io {
> };
>
> &hdmi {
> + avdd-0v9-supply = <&vdd_10>;
> + avdd-1v8-supply = <&vcc_18>;
> status = "okay";
> };
next prev parent reply other threads:[~2024-07-07 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 19:18 [PATCH] arm64: dts: rockchip: Add avdd supplies to hdmi on rock64 Diederik de Haas
2024-07-07 21:23 ` Dragan Simic [this message]
2024-07-08 9:55 ` Diederik de Haas
2024-07-09 8:40 ` Dragan Simic
2024-07-08 14:28 ` Heiko Stuebner
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=31a86ec073e1de9e0241845f8783cd6b@manjaro.org \
--to=dsimic@manjaro.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=heiko@sntech.de \
--cc=knaerzche@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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