From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] arm64: dts: renesas: ulcb-kf: adapt 1.8V HDMI regulator to schematics
Date: Mon, 12 Feb 2024 14:29:46 +0100 [thread overview]
Message-ID: <CAMuHMdXuWHCLa8HFXBZK4M4fqivudxjHcqqUyZ2=a3=OfFLPYQ@mail.gmail.com> (raw)
In-Reply-To: <20240129212350.33370-2-wsa+renesas@sang-engineering.com>
Hi Wolfram,
Thanks for your patch!
On Mon, Jan 29, 2024 at 10:23 PM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> It is named T1.8V in the schematics. Also add properties dcoumenting it
documenting
> is always on, also during boot.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> --- a/arch/arm64/boot/dts/renesas/ulcb-kf.dtsi
> +++ b/arch/arm64/boot/dts/renesas/ulcb-kf.dtsi
> @@ -32,11 +32,13 @@ hdmi1_con: endpoint {
> };
> };
>
> - hdmi_1v8: regulator-hdmi-1v8 {
> + t1v8: regulator-t1v8 {
"t1p8v"?
Or "reg_t1p8v", as the former is a rather short name, causing conflicts?
> compatible = "regulator-fixed";
> - regulator-name = "hdmi-1v8";
> + regulator-name = "t1v8";
> regulator-min-microvolt = <1800000>;
> regulator-max-microvolt = <1800000>;
> + regulator-boot-on;
> + regulator-always-on;
> };
>
> pcie_1v5: regulator-pcie-1v5 {
> @@ -154,11 +156,11 @@ hdmi@3d {
>
> pd-gpios = <&gpio_exp_75 5 GPIO_ACTIVE_LOW>;
>
> - avdd-supply = <&hdmi_1v8>;
> - dvdd-supply = <&hdmi_1v8>;
> - pvdd-supply = <&hdmi_1v8>;
> + avdd-supply = <&t1v8>;
> + dvdd-supply = <&t1v8>;
> + pvdd-supply = <&t1v8>;
> dvdd-3v-supply = <®_3p3v>;
> - bgvdd-supply = <&hdmi_1v8>;
> + bgvdd-supply = <&t1v8>;
>
> adi,input-depth = <8>;
> adi,input-colorspace = "rgb";
The rest LGTM.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-02-12 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 21:23 [RFC PATCH 0/2] arm64: dts: renesas: ulcb-kf: adapt regulators to schematics Wolfram Sang
2024-01-29 21:23 ` [RFC PATCH 1/2] arm64: dts: renesas: ulcb-kf: adapt 1.8V HDMI regulator " Wolfram Sang
2024-02-12 13:29 ` Geert Uytterhoeven [this message]
2024-02-12 13:42 ` Wolfram Sang
2024-02-12 13:44 ` Geert Uytterhoeven
2024-02-12 14:20 ` Wolfram Sang
2024-01-29 21:23 ` [RFC PATCH 2/2] arm64: dts: renesas: ulcb-kf: adapt sound 5v " Wolfram Sang
2024-02-12 13:37 ` Geert Uytterhoeven
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='CAMuHMdXuWHCLa8HFXBZK4M4fqivudxjHcqqUyZ2=a3=OfFLPYQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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;
as well as URLs for NNTP newsgroup(s).