From: Neha Malcom Francis <n-francis@ti.com>
To: "Kumar, Udit" <u-kumar1@ti.com>, <robh@kernel.org>,
<conor+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<vigneshr@ti.com>, <nm@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kristo@kernel.org>
Subject: Re: [PATCH 1/4] arm64: dts: ti: k3-j721e-mcu: Add the WKUP ESM instance
Date: Wed, 10 Apr 2024 11:09:42 +0530 [thread overview]
Message-ID: <3b009ce1-e5b3-4696-9c8a-995488a04cc7@ti.com> (raw)
In-Reply-To: <b76578ca-9e94-43a6-93cf-690e23545529@ti.com>
Hi Udit,
On 10/04/24 10:42, Kumar, Udit wrote:
> Hi Neha
>
> On 3/26/2024 5:57 PM, Neha Malcom Francis wrote:
>> Add the WKUP ESM instance for J721E. It has three instances in total,
>> one in the MAIN domain (main_esm) and two in the MCU-WKUP domain
>> (mcu_esm and wkup_esm).
>>
>> Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
>> ---
>> arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
>> b/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
>> index 4618b697fbc4..b0f41e9829cc 100644
>> --- a/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
>> @@ -689,4 +689,9 @@ mcu_esm: esm@40800000 {
>> ti,esm-pins = <95>;
>> bootph-pre-ram;
>> };
>> +
>> + wkup_esm: esm@42080000 {
>> + compatible = "ti,j721e-esm";
>> + reg = <0x00 0x42080000 0x00 0x1000>;
>
> I think , only esm@40800000 should be good for this SOC.
>
> I am not sure, why you want to add this. If you still want to add this for
> completeness ,
Yes, I wanted to make sure all ESM modules are present for DTS completeness.
>
> then two options, I suggest
>
> 1) If you plan to use this mention bootph-pre-ram and ti,esm-pins
>
No plans for using it as of now.
J721E ESM interrupt routing is such that the MAIN_ESM interrupt triggers an
error event in the MCU_ESM (which is correctly set via their node ti,j721e-esm
glue logic pins). The MCU_ESM and WKUP_ESM both generate the same interrupt
after. So there is no ti,j721e-esm pin applicable for WKUP_ESM.
> 2) In case , no plan to use this then please mark node as disabled
>
Yes I will mark this as disabled, I overlooked the fact that leaving this
enabled would throw "ESM init failed" when DT syncs with U-Boot. Thanks for
catching!
>
>> + };
>> };
--
Thanking You
Neha Malcom Francis
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-04-10 5:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 12:27 [PATCH 0/4] arm64: dts: ti: k3-j7*: Add missing ESM and watchdog nodes Neha Malcom Francis
2024-03-26 12:27 ` [PATCH 1/4] arm64: dts: ti: k3-j721e-mcu: Add the WKUP ESM instance Neha Malcom Francis
2024-04-10 5:12 ` Kumar, Udit
2024-04-10 5:39 ` Neha Malcom Francis [this message]
2024-03-26 12:27 ` [PATCH 2/4] arm64: dts: ti: k3-j721e-mcu: Add the MCU domain watchdog instances Neha Malcom Francis
2024-04-10 5:45 ` Kumar, Udit
2024-04-12 4:23 ` Neha Malcom Francis
2024-03-26 12:27 ` [PATCH 3/4] arm64: dts: ti: k3-j721e-main: Add the MAIN " Neha Malcom Francis
2024-04-10 5:36 ` Kumar, Udit
2024-04-10 5:50 ` Neha Malcom Francis
2024-04-12 4:21 ` Neha Malcom Francis
2024-03-26 12:27 ` [PATCH 4/4] arm64: dts: ti: k3-j7200-main: " Neha Malcom Francis
2024-04-10 6:05 ` Kumar, Udit
2024-04-10 6:09 ` Neha Malcom Francis
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=3b009ce1-e5b3-4696-9c8a-995488a04cc7@ti.com \
--to=n-francis@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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@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