From: Nishanth Menon <nm@ti.com>
To: Keerthy <j-keerthy@ti.com>
Cc: <robh+dt@kernel.org>, <vigneshr@ti.com>, <conor+dt@kernel.org>,
<kristo@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<u-kumar1@ti.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 5/7] arm64: dts: ti: k3-j784s4-mcu: Add the mcu domain watchdog instances
Date: Fri, 6 Oct 2023 06:44:22 -0500 [thread overview]
Message-ID: <20231006114422.avymeap7h5ocs6zq@dreadlock> (raw)
In-Reply-To: <20231006113410.tibvxxkeuujqnbv4@evolution>
> > + mcu_watchdog1: watchdog@40610000 {
> > + compatible = "ti,j7-rti-wdt";
> > + reg = <0x00 0x40610000 0x00 0x100>;
> > + clocks = <&k3_clks 368 1>;
> > + power-domains = <&k3_pds 368 TI_SCI_PD_EXCLUSIVE>;
> > + assigned-clocks = <&k3_clks 368 0>;
> > + assigned-clock-parents = <&k3_clks 368 4>;
>
> Please DONOT ignore the review comments - I did ask the documentation in
> dts as well. reason being that this is what people will see rather than
> dig up the commit log. it should be intutive when reading the dts why
> nodes are disabled by default Vs the standard of leaving it enabled by
> default. Given esp that these peripherals do not have anything to do
> with board semantics (pinmux or something similar) to be complete.
>
> > + status = "disabled";
Just providing clarifying comment - something like this is probably more
appropriate:
/* Tightly coupled to R5F */
status = "reserved";
The rti needs to be handled by R5F and is reserved for firmware usage.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2023-10-06 11:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 4:28 [PATCH v7 0/7] arm64: ti: k3-j7: Add the ESM & main domain watchdog nodes Keerthy
2023-10-06 4:28 ` [PATCH v7 1/7] arm64: dts: ti: k3-j721s2: Add ESM instances Keerthy
2023-10-06 4:28 ` [PATCH v7 2/7] arm64: dts: ti: k3-j784s4: " Keerthy
2023-10-06 4:28 ` [PATCH v7 3/7] arm64: dts: ti: k3-j7200: Add MCU domain ESM instance Keerthy
2023-10-06 4:28 ` [PATCH v7 4/7] arm64: dts: ti: k3-j784s4-main: Add the main domain watchdog instances Keerthy
2023-10-06 4:28 ` [PATCH v7 5/7] arm64: dts: ti: k3-j784s4-mcu: Add the mcu " Keerthy
2023-10-06 11:34 ` Nishanth Menon
2023-10-06 11:44 ` Nishanth Menon [this message]
2023-10-06 11:52 ` J, KEERTHY
2023-10-06 12:01 ` Nishanth Menon
2023-10-06 12:53 ` J, KEERTHY
2023-10-06 11:55 ` J, KEERTHY
2023-10-06 4:29 ` [PATCH v7 6/7] arm64: dts: ti: k3-j721s2-main: Add the main " Keerthy
2023-10-06 4:29 ` [PATCH v7 7/7] arm64: dts: ti: k3-j712s2-mcu: Add the mcu " 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=20231006114422.avymeap7h5ocs6zq@dreadlock \
--to=nm@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=robh+dt@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