From: "Kumar, Udit" <u-kumar1@ti.com>
To: Keerthy <j-keerthy@ti.com>, <robh+dt@kernel.org>, <nm@ti.com>,
<vigneshr@ti.com>, <conor+dt@kernel.org>, <kristo@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<u-kumar1@ti.com>
Subject: Re: [PATCH v3 0/7] arm64: ti: k3-j7: Add the ESM & main domain watchdog nodes
Date: Mon, 11 Sep 2023 13:56:49 +0530 [thread overview]
Message-ID: <a5c650c9-3bb5-44d7-8191-8e122f1077df@ti.com> (raw)
In-Reply-To: <20230911040942.31031-1-j-keerthy@ti.com>
Hi Keerthy
On 9/11/2023 9:39 AM, Keerthy wrote:
> The series add the ESM & main domain watchdog nodes for j721s2,
> j784s4 SOCs.
>
> Changes in v3:
>
> * Added all the RTI events for MAIN_ESM for j784s4 as 8 instances
> are enabled.
> * Rebased on top of 6.6-rc1
> * Tested for the watchdog reset
>
> RESEND series - corrected krzysztof.kozlowski+dt@linaro.org ID
>
> Changes in v2:
>
> * Added all the instances of watchdog on j784s4/j721s2
> * Fixed all 0x0 in dts to 0x00
> * Fixed couple of ESM event numbers for j721s2
> * Rebased to linux-next branch
>
> Keerthy (7):
> arm64: dts: ti: k3-j721s2: Add ESM instances
> arm64: dts: ti: k3-j784s4: Add ESM instances
> arm64: dts: ti: k3-j7200: Add MCU domain ESM instance
> arm64: dts: ti: k3-j784s4-main: Add the main domain watchdog instances
> arm64: dts: ti: k3-j784s4-mcu: Add the main domain watchdog instances
> arm64: dts: ti: k3-j721s2-main: Add the main domain watchdog instances
> arm64: dts: ti: k3-j721s2-mcu: Add the main domain watchdog instances
Thanks for series,
Two minor suggestions.
1) Order of patches , since J721S2 esm is added first , it will be
better to have watchdog for J721S2 first
2) I understand, to add watchdog entries, for J784S4 and J721S2, you
followed ascending device id order
due to that there is mix of entries like watchdog16 coming before
watchdog15.
Let maintainers to take call on these minor one.
For me, with or without above suggestions fix.
Reviewed-by: Udit Kumar <u-kumar1@ti.com>
> .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 6 +
> arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 94 +++++++++
> .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 32 +++
> arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 189 ++++++++++++++++++
> .../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 32 +++
> 5 files changed, 353 insertions(+)
>
prev parent reply other threads:[~2023-09-11 22:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 4:09 Keerthy
2023-09-11 4:09 ` [PATCH v3 1/7] arm64: dts: ti: k3-j721s2: Add ESM instances Keerthy
2023-09-11 4:09 ` [PATCH v3 2/7] arm64: dts: ti: k3-j784s4: " Keerthy
2023-09-25 5:29 ` Kumar, Udit
2023-09-11 4:09 ` [PATCH v3 3/7] arm64: dts: ti: k3-j7200: Add MCU domain ESM instance Keerthy
2023-09-11 4:09 ` [PATCH v3 4/7] arm64: dts: ti: k3-j784s4-main: Add the main domain watchdog instances Keerthy
2023-09-11 4:09 ` [PATCH v3 5/7] arm64: dts: ti: k3-j784s4-mcu: " Keerthy
2023-09-11 4:09 ` [PATCH v3 6/7] arm64: dts: ti: k3-j721s2-main: " Keerthy
2023-09-11 4:09 ` [PATCH v3 7/7] arm64: dts: ti: k3-j721s2-mcu: " Keerthy
2023-09-11 8:26 ` Kumar, Udit [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=a5c650c9-3bb5-44d7-8191-8e122f1077df@ti.com \
--to=u-kumar1@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=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®