From: Nishanth Menon <nm@ti.com>
To: "J, KEERTHY" <j-keerthy@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>, <robh+dt@kernel.org>,
<conor+dt@kernel.org>, <kristo@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <u-kumar1@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 2/7] arm64: dts: ti: k3-j784s4: Add ESM instances
Date: Thu, 5 Oct 2023 06:15:55 -0500 [thread overview]
Message-ID: <20231005111554.ol4vu4oxlensmx6m@booth> (raw)
In-Reply-To: <c7c32ec5-d0c1-443d-9851-3bb8e772c8fc@ti.com>
On 06:45-20231005, J, KEERTHY wrote:
>
>
> On 10/3/2023 12:20 PM, Vignesh Raghavendra wrote:
> >
> >
> > On 27/09/23 08:03, Keerthy wrote:
> > > Patch adds the ESM instances for j784s4. It has 3 instances.
> > > One in the main domain and two in the mcu-wakeup domian.
> > >
> > > Signed-off-by: Keerthy <j-keerthy@ti.com>
> > > ---
> > > arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 8 ++++++++
> > > arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 14 ++++++++++++++
> > > 2 files changed, 22 insertions(+)
> > >
> > > diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi b/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> > > index efed2d683f63..26dc3776f911 100644
> > > --- a/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> > > +++ b/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> > > @@ -1568,4 +1568,12 @@
> > > firmware-name = "j784s4-c71_3-fw";
> > > status = "disabled";
> > > };
> > > +
> > > + main_esm: esm@700000 {
> > > + compatible = "ti,j721e-esm";
> > > + reg = <0x00 0x700000 0x00 0x1000>;
> > > + ti,esm-pins = <688>, <689>, <690>, <691>, <692>, <693>, <694>,
> > > + <695>;
> > > + bootph-pre-ram;
> >
> > Similar to other nodes in this file, here and elsewhere use
> > bootph-all
>
> Okay. I will switch to bootph-all
Is'nt esm configuration just needed during pre-ram?
>
> >
> >
> > > + };
> > > };
> > > diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi
> > > index 4ab4018d3695..a7b5c4cb7d3e 100644
> > > --- a/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi
> > > +++ b/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi
> > > @@ -700,4 +700,18 @@
> > > status = "disabled";
> > > };
> > > };
> > > +
> > > + mcu_esm: esm@40800000 {
> > > + compatible = "ti,j721e-esm";
> > > + reg = <0x00 0x40800000 0x00 0x1000>;
> > > + ti,esm-pins = <95>;
> > > + bootph-pre-ram;
> > > + };
> > > +
> > > + wkup_esm: esm@42080000 {
> > > + compatible = "ti,j721e-esm";
> > > + reg = <0x00 0x42080000 0x00 0x1000>;
> > > + ti,esm-pins = <63>;
> > > + bootph-pre-ram;
> > > + };
> > > };
> >
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2023-10-05 14:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 2:33 [PATCH v6 0/7] arm64: ti: k3-j7: Add the ESM & main domain watchdog nodes Keerthy
2023-09-27 2:33 ` [PATCH v6 1/7] arm64: dts: ti: k3-j721s2: Add ESM instances Keerthy
2023-10-03 6:50 ` Vignesh Raghavendra
2023-10-05 1:15 ` J, KEERTHY
2023-09-27 2:33 ` [PATCH v6 2/7] arm64: dts: ti: k3-j784s4: " Keerthy
2023-10-03 6:50 ` Vignesh Raghavendra
2023-10-05 1:15 ` J, KEERTHY
2023-10-05 11:15 ` Nishanth Menon [this message]
2023-10-05 12:31 ` J, KEERTHY
2023-09-27 2:33 ` [PATCH v6 3/7] arm64: dts: ti: k3-j7200: Add MCU domain ESM instance Keerthy
2023-09-27 2:33 ` [PATCH v6 4/7] arm64: dts: ti: k3-j784s4-main: Add the main domain watchdog instances Keerthy
2023-10-03 6:48 ` Vignesh Raghavendra
2023-10-05 1:17 ` J, KEERTHY
2023-09-27 2:33 ` [PATCH v6 5/7] arm64: dts: ti: k3-j784s4-mcu: Add the mcu " Keerthy
2023-09-27 2:33 ` [PATCH v6 6/7] arm64: dts: ti: k3-j721s2-main: Add the main " Keerthy
2023-09-27 2:33 ` [PATCH v6 7/7] dts: ti: k3-j712s2-mcu: Add the mcu " Keerthy
2023-09-27 7:53 ` Krzysztof Kozlowski
2023-09-27 8:16 ` J, KEERTHY
2023-09-27 8:25 ` J, KEERTHY
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=20231005111554.ol4vu4oxlensmx6m@booth \
--to=nm@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=u-kumar1@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;
as well as URLs for NNTP newsgroup(s).