From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Nicolas Frattaroli" <nicolas.frattaroli@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-rockchip@lists.infradead.org>, <kernel@collabora.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] arm64: dts: rockchip: adjust dcin regulator on ROCK 4D
Date: Mon, 30 Jun 2025 20:12:27 +0200 [thread overview]
Message-ID: <DB02KKR1VK9H.1Q1Y5A98FKGLK@cknow.org> (raw)
In-Reply-To: <20250630-rock4d-reg-usb-wifi-v1-1-1057f412d98c@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 2331 bytes --]
Hi Nicolas,
On Mon Jun 30, 2025 at 5:36 PM CEST, Nicolas Frattaroli wrote:
> The ROCK 4D's actual DC input is 5V, and the schematic names it as being
> 5V as well.
>
> Rename the regulator, and change the voltage it claims to be at.
Shouldn't it have a fixes tag then? Providing 12V where 5V is expected
sounds problematic ;-)
> Furthermore, fix vcc_1v1_nldo_s3's vin-supply as coming from
> vcc_5v0_sys, and not the DCIN, as per the schematic. This makes no
> functional change; both regulators are always on, and one feeds into the
> other.
>
> Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
> ---
> arch/arm64/boot/dts/rockchip/rk3576-rock-4d.dts | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3576-rock-4d.dts b/arch/arm64/boot/dts/rockchip/rk3576-rock-4d.dts
> index 6756403111e704cad42f6674d5ab55eb0306f1e3..352e3df165688219bfedc19734d9eb32c547ec44 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3576-rock-4d.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3576-rock-4d.dts
> @@ -57,13 +57,13 @@ user-led {
> };
> };
>
> - vcc_12v0_dcin: regulator-vcc-12v0-dcin {
> + vcc_5v0_dcin: regulator-vcc-5v0-dcin {
> compatible = "regulator-fixed";
> regulator-always-on;
> regulator-boot-on;
> - regulator-min-microvolt = <12000000>;
> - regulator-max-microvolt = <12000000>;
> - regulator-name = "vcc_12v0_dcin";
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
> + regulator-name = "vcc_5v0_dcin";
> };
With the name change, this block needs to be moved down.
Cheers,
Diederik
>
> vcc_1v1_nldo_s3: regulator-vcc-1v1-nldo-s3 {
> @@ -166,7 +166,7 @@ vcc_5v0_device: regulator-vcc-5v0-device {
> regulator-min-microvolt = <5000000>;
> regulator-max-microvolt = <5000000>;
> regulator-name = "vcc_5v0_device";
> - vin-supply = <&vcc_12v0_dcin>;
> + vin-supply = <&vcc_5v0_sys>;
> };
>
> vcc_5v0_host: regulator-vcc-5v0-host {
> @@ -190,7 +190,7 @@ vcc_5v0_sys: regulator-vcc-5v0-sys {
> regulator-min-microvolt = <5000000>;
> regulator-max-microvolt = <5000000>;
> regulator-name = "vcc_5v0_sys";
> - vin-supply = <&vcc_12v0_dcin>;
> + vin-supply = <&vcc_5v0_dcin>;
> };
> };
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-06-30 18:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 15:36 [PATCH 0/3] ROCK 4D DT additions: regulators, usb, rfkill Nicolas Frattaroli
2025-06-30 15:36 ` [PATCH 1/3] arm64: dts: rockchip: adjust dcin regulator on ROCK 4D Nicolas Frattaroli
2025-06-30 18:12 ` Diederik de Haas [this message]
2025-06-30 23:10 ` Sebastian Reichel
2025-07-01 8:19 ` Diederik de Haas
2025-07-01 8:55 ` Nicolas Frattaroli
2025-07-01 9:07 ` Diederik de Haas
2025-06-30 15:36 ` [PATCH 2/3] arm64: dts: rockchip: complete USB nodes " Nicolas Frattaroli
2025-06-30 15:36 ` [PATCH 3/3] arm64: dts: rockchip: theoretically enable Wi-Fi " Nicolas Frattaroli
2025-07-10 9:27 ` [PATCH 0/3] ROCK 4D DT additions: regulators, usb, rfkill 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=DB02KKR1VK9H.1Q1Y5A98FKGLK@cknow.org \
--to=didi.debian@cknow.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nicolas.frattaroli@collabora.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).