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 4/4] arm64: dts: ti: k3-j7200-main: Add the MAIN domain watchdog instances
Date: Wed, 10 Apr 2024 11:39:43 +0530 [thread overview]
Message-ID: <bb464315-26ea-48d7-8407-df4b132fbcfa@ti.com> (raw)
In-Reply-To: <f999020f-0f07-4eb3-bc59-f1a0f7237af7@ti.com>
Hi Udit
On 10/04/24 11:35, Kumar, Udit wrote:
> Hi Neha
>
> On 3/26/2024 5:57 PM, Neha Malcom Francis wrote:
>> There are 4 watchdog instances in the MAIN domain:
>> * one each for the 2 A72 cores
>> * one each for the 2 R5F cores
>>
>> Currently, the devicetree only describes watchdog instances for the A72
>> cores and enables them. Describe the remaining but reserve them as they
>> will be used by their respective firmware.
>>
>> Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
>> ---
>> arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 27 +++++++++++++++++++++++
>> 1 file changed, 27 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
>> b/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
>> index 657f9cc9f4ea..c448c2218e23 100644
>> --- a/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
>> @@ -1254,6 +1254,33 @@ watchdog1: watchdog@2210000 {
>> assigned-clock-parents = <&k3_clks 253 5>;
>> };
>> + /*
>> + * The following RTI instances are coupled with MCU R5Fs so
>> + * keeping them reserved as these will be used by their respective
>> + * firmware
>> + */
>> + watchdog2: watchdog@23c0000 {
>> + compatible = "ti,j7-rti-wdt";
>> + reg = <0x00 0x23c0000 0x00 0x100>;
>> + clocks = <&k3_clks 258 1>;
>> + power-domains = <&k3_pds 258 TI_SCI_PD_EXCLUSIVE>;
>> + assigned-clocks = <&k3_clks 258 1>;
>> + assigned-clock-parents = <&k3_clks 258 5>;
>> + /* reserved for MAIN_R5F0_0 */
>> + status = "reserved";
>> + };
>> +
>> + watchdog3: watchdog@23d0000 {
>> + compatible = "ti,j7-rti-wdt";
>> + reg = <0x00 0x23d0000 0x00 0x100>;
>> + clocks = <&k3_clks 259 1>;
>> + power-domains = <&k3_pds 259 TI_SCI_PD_EXCLUSIVE>;
>> + assigned-clocks = <&k3_clks 259 1>;
>> + assigned-clock-parents = <&k3_clks 259 5>;
>> + /* reserved for MAIN_R5F0_1 */
>> + status = "reserved";
>> + };
>> +
>
> Please see, if this make more sense to have label as watchdog28 and watchdog29,
> to align with TRM.
Yes I will change all the patches in the series to align with TRM numbering.
>
> Also request to add mcu domain 2 watchdog as well.
Oh I had missed that out, will add it in v2.
>
>
>> main_timer0: timer@2400000 {
>> compatible = "ti,am654-timer";
>> reg = <0x00 0x2400000 0x00 0x400>;
--
Thanking You
Neha Malcom Francis
prev parent reply other threads:[~2024-04-10 6:09 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
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 [this message]
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=bb464315-26ea-48d7-8407-df4b132fbcfa@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