Devicetree
 help / color / mirror / Atom feed
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 2/4] arm64: dts: ti: k3-j721e-mcu: Add the MCU domain watchdog instances
Date: Fri, 12 Apr 2024 09:53:27 +0530	[thread overview]
Message-ID: <400cc67d-1d86-4fd5-ba1a-ef6bb166d0a0@ti.com> (raw)
In-Reply-To: <2455386b-cf9c-4060-ba86-34ea80a5af6a@ti.com>

Hi Udit,

On 10/04/24 11:15, Kumar, Udit wrote:
> Hi Neha
> 
> On 3/26/2024 5:57 PM, Neha Malcom Francis wrote:
>> There are 2 watchdog instances in the MCU domain. These instances are
>> coupled with the MCU domain R55 instances. Reserve them as they are not
>> used by A72.
>>
>> Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
>> ---
>>   .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi      | 26 +++++++++++++++++++
>>   1 file changed, 26 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 b0f41e9829cc..867f307909be 100644
>> --- a/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
>> @@ -694,4 +694,30 @@ wkup_esm: esm@42080000 {
>>           compatible = "ti,j721e-esm";
>>           reg = <0x00 0x42080000 0x00 0x1000>;
>>       };
>> +
>> +    /*
>> +     * The 2 RTI instances are couple with MCU R5Fs so keeping them
>> +     * reserved as these will be used by their respective firmware
>> +     */
>> +    mcu_watchdog0: watchdog@40600000 {
>> +        compatible = "ti,j7-rti-wdt";
>> +        reg = <0x00 0x40600000 0x00 0x100>;
>> +        clocks = <&k3_clks 262 1>;
>> +        power-domains = <&k3_pds 262 TI_SCI_PD_EXCLUSIVE>;
>> +        assigned-clocks = <&k3_clks 262 1>;
>> +        assigned-clock-parents = <&k3_clks 262 5>;
>> +        /* reserved for MCU_R5F0_0 */
>> +        status = "reserved";
>> +    };
>> +
>> +    mcu_watchdog1: watchdog@40610000 {
>> +        compatible = "ti,j7-rti-wdt";
>> +        reg = <0x00 0x40610000 0x00 0x100>;
>> +        clocks = <&k3_clks 263 1>;
>> +        power-domains = <&k3_pds 263 TI_SCI_PD_EXCLUSIVE>;
>> +        assigned-clocks = <&k3_clks 263 1>;
>> +        assigned-clock-parents = <&k3_clks 263 5>;
>> +        /* reserved for MCU_R5F0_1 */
> 
> Table 12-22642. MCU_RTI Hardware Requests (In same TRM referred in 3/4 patch 
> review ),
> 
> says each WDT has destination of MCU0_R5_CORE0 and MCU0_R5_CORE1
> 
> Please suggest, if fw level this is decided to reserved like above ?
> 
> With that clarification, Please use
> 
> Reviewed-by: Udit Kumar <u-kumar1@ti.com>
> 
> 

At firmware level, the MCU R5 is in lockstep mode. The dual destination of the 
WDT interrupt makes sense then.

>> +        status = "reserved";
>> +    };
>>   };

-- 
Thanking You
Neha Malcom Francis

  reply	other threads:[~2024-04-12  4:23 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
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 [this message]
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=400cc67d-1d86-4fd5-ba1a-ef6bb166d0a0@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