From: Rishikesh Donadkar <r-donadkar@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>, <devarsht@ti.com>,
<y-abhilashchandra@ti.com>, <s-jain1@ti.com>,
<jai.luthra@linux.dev>, <jai.luthra@ideasonboard.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<imx@lists.linux.dev>, <r-donadkar@ti.com>
Subject: [PATCH v1 1/4] arm64: dts: ti: k3-am62p5-sk: Add regulator nodes for AM62P
Date: Tue, 29 Apr 2025 21:11:30 +0530 [thread overview]
Message-ID: <20250429154133.3377962-2-r-donadkar@ti.com> (raw)
In-Reply-To: <20250429154133.3377962-1-r-donadkar@ti.com>
Add regulator node for AM62P-SK
VCC_3V3_MAIN is the output of LM5141-Q1, and it serves as an input to
TPS22965DSGT which produces VCC_3V3_SYS [1]
VCC_3V3_SYS servers as vin-supply for peripherals like CSI [1].
Link: https://www.ti.com/lit/zip/sprr487 [1]
Signed-off-by: Rishikesh Donadkar <r-donadkar@ti.com>
---
arch/arm64/boot/dts/ti/k3-am62p5-sk.dts | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts b/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts
index c2f55cc5a8ebc..0af33fccb96bf 100644
--- a/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts
+++ b/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts
@@ -115,6 +115,28 @@ vddshv_sdio: regulator-3 {
bootph-all;
};
+ vcc_3v3_main: regulator-4 {
+ /* output of LM5141-Q1 */
+ compatible = "regulator-fixed";
+ regulator-name = "vcc_3v3_main";
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
+ vin-supply = <&vmain_pd>;
+ regulator-always-on;
+ regulator-boot-on;
+ };
+
+ vcc_3v3_sys: regulator-5 {
+ /* output of TPS222965DSGT */
+ compatible = "regulator-fixed";
+ regulator-name = "vcc_3v3_sys";
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
+ vin-supply = <&vcc_3v3_main>;
+ regulator-always-on;
+ regulator-boot-on;
+ };
+
leds {
compatible = "gpio-leds";
pinctrl-names = "default";
--
2.34.1
next prev parent reply other threads:[~2025-04-29 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 15:41 [PATCH v1 0/4] Fix dtbs_check warnings in sensor overlays Rishikesh Donadkar
2025-04-29 15:41 ` Rishikesh Donadkar [this message]
2025-05-02 7:48 ` [PATCH v1 1/4] arm64: dts: ti: k3-am62p5-sk: Add regulator nodes for AM62P Devarsh Thakkar
2025-04-29 15:41 ` [PATCH v1 2/4] arm64: dts: ti: k3-am62x: Add required voltage supplies for IMX219 Rishikesh Donadkar
2025-05-02 8:07 ` Devarsh Thakkar
2025-05-02 8:15 ` Devarsh Thakkar
2025-05-02 11:09 ` Donadkar, Rishikesh
2025-04-29 15:41 ` [PATCH v1 3/4] arm64: dts: ti: k3-am62x: Add required voltage supplies for OV5640 Rishikesh Donadkar
2025-05-02 8:43 ` Devarsh Thakkar
2025-04-29 15:41 ` [PATCH v1 4/4] arm64: dts: ti: k3-am62x: Add required voltage supplies for TEVI-OV5640 Rishikesh Donadkar
2025-05-02 9:07 ` Devarsh Thakkar
2025-05-02 11:13 ` Donadkar, Rishikesh
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=20250429154133.3377962-2-r-donadkar@ti.com \
--to=r-donadkar@ti.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=jai.luthra@ideasonboard.com \
--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=s-jain1@ti.com \
--cc=vaishnav.a@ti.com \
--cc=vigneshr@ti.com \
--cc=y-abhilashchandra@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