From: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>
Cc: <kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <vaishnav.a@ti.com>,
<jai.luthra@linux.dev>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <imx@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <u-kumar1@ti.com>,
<y-abhilashchandra@ti.com>
Subject: [PATCH 2/5] arm64: dts: ti: am68-sk: Fix power regulator hierarchy
Date: Tue, 1 Apr 2025 17:10:50 +0530 [thread overview]
Message-ID: <20250401114053.229534-3-y-abhilashchandra@ti.com> (raw)
In-Reply-To: <20250401114053.229534-1-y-abhilashchandra@ti.com>
Add a fixed regulator node for the LM61460 5V supply on the AM68 SK and
fix the vin-supply for the TLV71033 regulator on AM68-SK by updating it
from vsys_3v3 to vsys_5v0 to match the schematics.
AM68-SK schematics: https://www.ti.com/lit/zip/sprr463
Fixes: a266c180b398 ("arm64: dts: ti: k3-am68-sk: Add support for AM68 SK base board")
Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
---
arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts b/arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts
index 11522b36e0ce..5fa70a874d7b 100644
--- a/arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts
+++ b/arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts
@@ -44,6 +44,17 @@ vusb_main: regulator-vusb-main5v0 {
regulator-boot-on;
};
+ vsys_5v0: regulator-vsys5v0 {
+ /* Output of LM61460 */
+ compatible = "regulator-fixed";
+ regulator-name = "vsys_5v0";
+ regulator-min-microvolt = <5000000>;
+ regulator-max-microvolt = <5000000>;
+ vin-supply = <&vusb_main>;
+ regulator-always-on;
+ regulator-boot-on;
+ };
+
vsys_3v3: regulator-vsys3v3 {
/* Output of LM5141 */
compatible = "regulator-fixed";
@@ -76,7 +87,7 @@ vdd_sd_dv: regulator-tlv71033 {
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <3300000>;
regulator-boot-on;
- vin-supply = <&vsys_3v3>;
+ vin-supply = <&vsys_5v0>;
gpios = <&main_gpio0 49 GPIO_ACTIVE_HIGH>;
states = <1800000 0x0>,
<3300000 0x1>;
--
2.34.1
next prev parent reply other threads:[~2025-04-01 11:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 11:40 [PATCH 0/5] Fix dtbs_check warnings in CSI overlays Yemike Abhilash Chandra
2025-04-01 11:40 ` [PATCH 1/5] arm64: dts: ti: j721e-sk: Add DT nodes for power regulators Yemike Abhilash Chandra
2025-04-07 13:41 ` Nishanth Menon
2025-04-08 8:45 ` Yemike Abhilash Chandra
2025-04-01 11:40 ` Yemike Abhilash Chandra [this message]
2025-04-01 11:40 ` [PATCH 3/5] arm64: dts: ti: k3-j721e-sk: Fix dtbs_check warnings in IMX219 overlay Yemike Abhilash Chandra
2025-04-07 13:45 ` Nishanth Menon
2025-04-08 9:01 ` Yemike Abhilash Chandra
2025-04-08 12:17 ` Nishanth Menon
2025-04-01 11:40 ` [PATCH 4/5] arm64: dts: ti: k3-am62x: Fix a few minor " Yemike Abhilash Chandra
2025-04-01 11:40 ` [PATCH 5/5] arm64: dts: ti: k3-am62x: Rename I2C switch to I2C mux in OV5640 overlay Yemike Abhilash Chandra
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=20250401114053.229534-3-y-abhilashchandra@ti.com \
--to=y-abhilashchandra@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=jai.luthra@linux.dev \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vaishnav.a@ti.com \
--cc=vigneshr@ti.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