From: "Kumar, Udit" <u-kumar1@ti.com>
To: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>, <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>, <stable@vger.kernel.org>
Subject: Re: [PATCH v2 2/7] arm64: dts: ti: am68-sk: Fix regulator hierarchy
Date: Fri, 11 Apr 2025 19:16:05 +0530 [thread overview]
Message-ID: <6b730f33-9d83-4ced-839d-dc03b2eb8e4c@ti.com> (raw)
In-Reply-To: <20250409134128.2098195-3-y-abhilashchandra@ti.com>
On 4/9/2025 7:11 PM, Yemike Abhilash Chandra wrote:
> Update the vin-supply of the TLV71033 regulator from LM5141 (vsys_3v3) to
> LM61460 (vsys_5v0) to match the schematics. Add a fixed regulator node for
> the LM61460 5V supply to support this change.
>
> 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")
> Cc: stable@vger.kernel.org
> 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>;
Looking at schematic page -3
USB PD Controller is giving input to LM61460 , LM5141(3V3), and TPS62177.
Could you please recheck this, vin-supply for 3v3 regulator
Thanks
Udit
> gpios = <&main_gpio0 49 GPIO_ACTIVE_HIGH>;
> states = <1800000 0x0>,
> <3300000 0x1>;
next prev parent reply other threads:[~2025-04-11 13:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 13:41 [PATCH v2 0/7] Fix dtbs_check warnings in CSI overlays Yemike Abhilash Chandra
2025-04-09 13:41 ` [PATCH v2 1/7] arm64: dts: ti: j721e-sk: Add DT nodes for power regulators Yemike Abhilash Chandra
2025-04-11 13:32 ` Francis, Neha
2025-04-11 13:34 ` Kumar, Udit
2025-04-14 11:50 ` Yemike Abhilash Chandra
2025-04-09 13:41 ` [PATCH v2 2/7] arm64: dts: ti: am68-sk: Fix regulator hierarchy Yemike Abhilash Chandra
2025-04-11 13:46 ` Kumar, Udit [this message]
2025-04-11 13:50 ` Francis, Neha
2025-04-11 17:29 ` Kumar, Udit
2025-04-09 13:41 ` [PATCH v2 3/7] arm64: dts: ti: k3-j721e-sk: Remove clock-names property from IMX219 overlay Yemike Abhilash Chandra
2025-04-11 13:36 ` Francis, Neha
2025-04-14 6:47 ` Jai Luthra
2025-04-09 13:41 ` [PATCH v2 4/7] arm64: dts: ti: k3-j721e-sk: Add requiried voltage supplies for IMX219 Yemike Abhilash Chandra
2025-04-11 13:38 ` Francis, Neha
2025-04-14 11:40 ` Yemike Abhilash Chandra
2025-04-09 13:41 ` [PATCH v2 5/7] arm64: dts: ti: k3-am62x: Remove clock-names property from IMX219 overlay Yemike Abhilash Chandra
2025-04-11 13:39 ` Francis, Neha
2025-04-14 6:48 ` Jai Luthra
2025-04-09 13:41 ` [PATCH v2 6/7] arm64: dts: ti: k3-am62x: Rename I2C switch to I2C mux in " Yemike Abhilash Chandra
2025-04-11 13:40 ` Francis, Neha
2025-04-14 6:49 ` Jai Luthra
2025-04-09 13:41 ` [PATCH v2 7/7] arm64: dts: ti: k3-am62x: Rename I2C switch to I2C mux in OV5640 overlay Yemike Abhilash Chandra
2025-04-11 13:42 ` Francis, Neha
2025-04-14 6:50 ` Jai Luthra
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=6b730f33-9d83-4ced-839d-dc03b2eb8e4c@ti.com \
--to=u-kumar1@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=stable@vger.kernel.org \
--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