From: "Kumar, Udit" <u-kumar1@ti.com>
To: Keerthy <j-keerthy@ti.com>, <robh+dt@kernel.org>, <nm@ti.com>,
<vigneshr@ti.com>, <conor+dt@kernel.org>, <kristo@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/7] arm64: dts: ti: k3-j784s4: Add ESM instances
Date: Mon, 25 Sep 2023 10:59:13 +0530 [thread overview]
Message-ID: <2cc9060f-b44d-a870-6b98-20f17b2feac1@ti.com> (raw)
In-Reply-To: <20230911040942.31031-3-j-keerthy@ti.com>
On 9/11/2023 9:39 AM, 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 | 7 +++++++
> arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 12 ++++++++++++
> 2 files changed, 19 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..02d549a2ca06 100644
> --- a/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> @@ -1568,4 +1568,11 @@
> 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>;
> + };
> };
> 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..f1dfa4144168 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,16 @@
> status = "disabled";
> };
> };
> +
> + mcu_esm: esm@40800000 {
> + compatible = "ti,j721e-esm";
> + reg = <0x00 0x40800000 0x00 0x1000>;
> + ti,esm-pins = <95>;
> + };
> +
> + wkup_esm: esm@42080000 {
> + compatible = "ti,j721e-esm";
> + reg = <0x00 0x42080000 0x00 0x1000>;
> + ti,esm-pins = <63>;
> + };
Please consider adding bootph node for esm,
I understand these nodes will be used in R5/SPL
Thanks
> };
next prev parent reply other threads:[~2023-09-25 5:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 4:09 [PATCH v3 0/7] arm64: ti: k3-j7: Add the ESM & main domain watchdog nodes Keerthy
2023-09-11 4:09 ` [PATCH v3 1/7] arm64: dts: ti: k3-j721s2: Add ESM instances Keerthy
2023-09-11 4:09 ` [PATCH v3 2/7] arm64: dts: ti: k3-j784s4: " Keerthy
2023-09-25 5:29 ` Kumar, Udit [this message]
2023-09-11 4:09 ` [PATCH v3 3/7] arm64: dts: ti: k3-j7200: Add MCU domain ESM instance Keerthy
2023-09-11 4:09 ` [PATCH v3 4/7] arm64: dts: ti: k3-j784s4-main: Add the main domain watchdog instances Keerthy
2023-09-11 4:09 ` [PATCH v3 5/7] arm64: dts: ti: k3-j784s4-mcu: " Keerthy
2023-09-11 4:09 ` [PATCH v3 6/7] arm64: dts: ti: k3-j721s2-main: " Keerthy
2023-09-11 4:09 ` [PATCH v3 7/7] arm64: dts: ti: k3-j721s2-mcu: " Keerthy
2023-09-11 8:26 ` [PATCH v3 0/7] arm64: ti: k3-j7: Add the ESM & main domain watchdog nodes Kumar, Udit
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=2cc9060f-b44d-a870-6b98-20f17b2feac1@ti.com \
--to=u-kumar1@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=nm@ti.com \
--cc=robh+dt@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®