From: "Kumar, Udit" <u-kumar1@ti.com>
To: Andrew Halaney <ahalaney@redhat.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Keerthy <j-keerthy@ti.com>,
Neha Malcom Francis <n-francis@ti.com>,
Eric Chanudet <echanude@redhat.com>,
Enric Balletbo <eballetb@redhat.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Manorit Chawdhry <m-chawdhry@ti.com>
Subject: Re: [PATCH RFC/RFT 1/2] arm64: dts: ti: k3-j784s4-evm: Mark tps659413 and children as bootph-all
Date: Sat, 7 Sep 2024 11:04:50 +0530 [thread overview]
Message-ID: <bd188c0d-9fa1-4350-8787-36af319c7930@ti.com> (raw)
In-Reply-To: <20240906-j784s4-tps6594-bootph-v1-1-c5b58d43bf04@redhat.com>
Thanks for your patch Andrew
On 9/7/2024 2:51 AM, Andrew Halaney wrote:
> In order for the MCU domain to access this PMIC and its children in
> u-boot SPL, the nodes need to be marked appropriately otherwise they
> are not seen by SPL.
>
> This is necessary if the MCU domain is to program the TPS6594 MCU ESM
> state machine, which is required to wire up the watchdog in a manner
> that will reset the board.
>
> Signed-off-by: Andrew Halaney <ahalaney@redhat.com>
> ---
> arch/arm64/boot/dts/ti/k3-j784s4-evm.dts | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-evm.dts b/arch/arm64/boot/dts/ti/k3-j784s4-evm.dts
> index 6695ebbcb4d0..044a428136df 100644
> --- a/arch/arm64/boot/dts/ti/k3-j784s4-evm.dts
> +++ b/arch/arm64/boot/dts/ti/k3-j784s4-evm.dts
> @@ -642,6 +642,7 @@ eeprom@50 {
> };
>
> tps659413: pmic@48 {
> + bootph-all;
> compatible = "ti,tps6594-q1";
> reg = <0x48>;
> system-power-controller;
> @@ -662,7 +663,10 @@ tps659413: pmic@48 {
> ldo4-supply = <&vsys_3v3>;
>
> regulators {
> + bootph-all;
> +
> bucka12: buck12 {
> + bootph-all;
Add bootph in on regulator node should be enough,
As I see SPL/u-boot does not need all nodes.
FYI,
Similar series in review
https://lore.kernel.org/all/20240814-b4-upstream-bootph-all-v4-0-f2b462000f25@ti.com/
> regulator-name = "vdd_ddr_1v1";
> regulator-min-microvolt = <1100000>;
> regulator-max-microvolt = <1100000>;
> @@ -671,6 +675,7 @@ bucka12: buck12 {
> };
>
> bucka3: buck3 {
> + bootph-all;
> regulator-name = "vdd_ram_0v85";
> regulator-min-microvolt = <850000>;
> regulator-max-microvolt = <850000>;
> @@ -679,6 +684,7 @@ bucka3: buck3 {
> };
>
> bucka4: buck4 {
> + bootph-all;
> regulator-name = "vdd_io_1v8";
> regulator-min-microvolt = <1800000>;
> regulator-max-microvolt = <1800000>;
> @@ -687,6 +693,7 @@ bucka4: buck4 {
> };
>
> bucka5: buck5 {
> + bootph-all;
> regulator-name = "vdd_mcu_0v85";
> regulator-min-microvolt = <850000>;
> regulator-max-microvolt = <850000>;
> @@ -695,6 +702,7 @@ bucka5: buck5 {
> };
>
> ldoa1: ldo1 {
> + bootph-all;
> regulator-name = "vdd_mcuio_1v8";
> regulator-min-microvolt = <1800000>;
> regulator-max-microvolt = <1800000>;
> @@ -703,6 +711,7 @@ ldoa1: ldo1 {
> };
>
> ldoa2: ldo2 {
> + bootph-all;
> regulator-name = "vdd_mcuio_3v3";
> regulator-min-microvolt = <3300000>;
> regulator-max-microvolt = <3300000>;
> @@ -711,6 +720,7 @@ ldoa2: ldo2 {
> };
>
> ldoa3: ldo3 {
> + bootph-all;
> regulator-name = "vds_dll_0v8";
> regulator-min-microvolt = <800000>;
> regulator-max-microvolt = <800000>;
> @@ -719,6 +729,7 @@ ldoa3: ldo3 {
> };
>
> ldoa4: ldo4 {
> + bootph-all;
> regulator-name = "vda_mcu_1v8";
> regulator-min-microvolt = <1800000>;
> regulator-max-microvolt = <1800000>;
>
next prev parent reply other threads:[~2024-09-07 5:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 21:21 [PATCH RFC/RFT 0/2] arm64: dts: ti: k3-j784s4: " Andrew Halaney
2024-09-06 21:21 ` [PATCH RFC/RFT 1/2] arm64: dts: ti: k3-j784s4-evm: " Andrew Halaney
2024-09-07 5:34 ` Kumar, Udit [this message]
2024-09-10 17:20 ` Andrew Halaney
2024-09-11 4:24 ` Kumar, Udit
2024-09-06 21:21 ` [PATCH RFC/RFT 2/2] arm64: dts: ti: k3-am69-sk: " Andrew Halaney
2024-09-09 16:32 ` [PATCH RFC/RFT 0/2] arm64: dts: ti: k3-j784s4: " Andrew Halaney
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=bd188c0d-9fa1-4350-8787-36af319c7930@ti.com \
--to=u-kumar1@ti.com \
--cc=ahalaney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eballetb@redhat.com \
--cc=echanude@redhat.com \
--cc=j-keerthy@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--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
all inboxes | Powered by JetHome®