From: Nishanth Menon <nm@ti.com>
To: Bryan Brattlof <bb@ti.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Julien Panis <jpanis@baylibre.com>
Subject: Re: [PATCH 2/2] arm64: dts: ti: k3-am62: Add watchdog nodes
Date: Mon, 20 Mar 2023 10:44:41 -0500 [thread overview]
Message-ID: <20230320154441.ayijqbxcdgv4lzkn@cyclist> (raw)
In-Reply-To: <20230320153649.zfmyhk65ngh4u35d@bryanbrattlof.com>
On 10:36-20230320, Bryan Brattlof wrote:
> > + main_rti4: watchdog@e0f0000 {
> > + compatible = "ti,j7-rti-wdt";
> > + reg = <0x00 0x0e0f0000 0x00 0x100>;
> > + clocks = <&k3_clks 130 0>;
> > + power-domains = <&k3_pds 130 TI_SCI_PD_EXCLUSIVE>;
> > + assigned-clocks = <&k3_clks 130 0>;
> > + assigned-clock-parents = <&k3_clks 130 2>;
> > + };
> > +
>
> This may be a dumb question, though the ti-sci and TRM documentation is
> labeling this as rti15? idk if we should label this the same? it might
> make grepping a little easier :)
Sure, will fix.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
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:[~2023-03-20 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 10:58 [PATCH 0/2] arm64: dts: ti: k3-am62: Add watchdog and rtc nodes Nishanth Menon
2023-03-11 10:58 ` [PATCH 1/2] arm64: dts: ti: k3-am62-wakeup: Introduce RTC node Nishanth Menon
2023-03-11 10:58 ` [PATCH 2/2] arm64: dts: ti: k3-am62: Add watchdog nodes Nishanth Menon
2023-03-20 15:36 ` Bryan Brattlof
2023-03-20 15:44 ` Nishanth Menon [this message]
2023-03-20 15:37 ` [PATCH 0/2] arm64: dts: ti: k3-am62: Add watchdog and rtc nodes Bryan Brattlof
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=20230320154441.ayijqbxcdgv4lzkn@cyclist \
--to=nm@ti.com \
--cc=bb@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jpanis@baylibre.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=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