From: "J, KEERTHY" <j-keerthy@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: <vigneshr@ti.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<kristo@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/5] arm64: dts: ti: k3-j721s2-main: Add main domain watchdog entries
Date: Thu, 31 Aug 2023 19:10:38 +0530 [thread overview]
Message-ID: <78431d87-ea56-138b-d2f7-6b27b7d83dc1@ti.com> (raw)
In-Reply-To: <20230831114830.oenlyvwyxbi2uerq@deserving>
On 8/31/2023 5:18 PM, Nishanth Menon wrote:
> On 12:56-20230830, Keerthy wrote:
>> Add DT entries for main domain watchdog instances.
>>
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>> ---
>> arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 18 ++++++++++++++++++
>> 1 file changed, 18 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi
>> index 87841bcc509d..33276d31faa1 100644
>> --- a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi
>> @@ -1513,4 +1513,22 @@
>> reg = <0x0 0x700000 0x0 0x1000>;
>> ti,esm-pins = <344>, <345>;
>> };
>> +
>> + watchdog0: watchdog@2200000 {
>> + compatible = "ti,j7-rti-wdt";
>> + reg = <0x0 0x2200000 0x0 0x100>;
>> + clocks = <&k3_clks 286 1>;
>> + power-domains = <&k3_pds 286 TI_SCI_PD_EXCLUSIVE>;
>> + assigned-clocks = <&k3_clks 286 1>;
>> + assigned-clock-parents = <&k3_clks 286 5>;
>> + };
>> +
>> + watchdog1: watchdog@2210000 {
>> + compatible = "ti,j7-rti-wdt";
>> + reg = <0x0 0x2210000 0x0 0x100>;
>> + clocks = <&k3_clks 287 1>;
>> + power-domains = <&k3_pds 287 TI_SCI_PD_EXCLUSIVE>;
>> + assigned-clocks = <&k3_clks 287 1>;
>> + assigned-clock-parents = <&k3_clks 287 5>;
>> + };
>
> Are these all the wdts in main domain - do define and leave the other wdts
> disabled as they are tightly coupled to other processors (and must be
> enabled by the OS running on them), but defining them allows us to reuse
> the definitions in OSes running on R5s (for instance) to reuse the same
> device definitions.
Hello Nishanth,
Okay. I will add all the remaining ones & keep them disabled.
Thanks for the feedback.
Regards,
Keerthy
>
>> };
>> --
>> 2.17.1
>>
>
next prev parent reply other threads:[~2023-08-31 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 7:26 [PATCH 0/5] arm64: ti: k3-j7: Add the ESM & main domain watchdog nodes Keerthy
2023-08-30 7:26 ` [PATCH 1/5] arm64: dts: ti: k3-j721s2: Add ESM instances Keerthy
2023-08-30 7:26 ` [PATCH 2/5] arm64: dts: ti: k3-j784s4: " Keerthy
2023-08-30 7:26 ` [PATCH 3/5] arm64: dts: ti: k3-j7200: Add MCU domain ESM instance Keerthy
2023-08-30 7:26 ` [PATCH 4/5] arm64: dts: ti: k3-j721s2-main: Add main domain watchdog entries Keerthy
2023-08-31 11:48 ` Nishanth Menon
2023-08-31 13:40 ` J, KEERTHY [this message]
2023-08-30 7:26 ` [PATCH 5/5] arm64: dts: ti: k3-j784s4-main: " 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=78431d87-ea56-138b-d2f7-6b27b7d83dc1@ti.com \
--to=j-keerthy@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+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®