From: Keerthy <j-keerthy@ti.com>
To: <robh+dt@kernel.org>, <nm@ti.com>, <vigneshr@ti.com>,
<conor+dt@kernel.org>, <kristo@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>
Cc: <j-keerthy@ti.com>, <u-kumar1@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v8 0/7] arm64: ti: k3-j7: Add the ESM & main domain watchdog nodes
Date: Sun, 8 Oct 2023 10:16:50 +0530 [thread overview]
Message-ID: <20231008044657.25788-1-j-keerthy@ti.com> (raw)
The series add the ESM & main domain watchdog nodes for j721s2,
j784s4 SOCs.
Changes in v8:
* Changed the status of non-MPU nodes from disabled to reserved
* Added inline comments to the reserved RTI nodes
Changes in v7:
* Rebased on top of ti-next branch
* Reordered the watchdog nodes based on the addresses.
* Changed the watchdog numbering.
Changes in v5/v6:
* Updated commit log and added comments for MCU & non-A72 watchdog
instances disabling.
Changes in v4:
* Added bootph-pre-ram for all the ESM instances needed for SPL.
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 mcu domain watchdog instances
arm64: dts: ti: k3-j721s2-main: Add the main domain watchdog instances
arm64: dts: ti: k3-j712s2-mcu: Add the mcu domain watchdog instances
.../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 7 +
arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 107 +++++++++
.../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 40 ++++
arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 206 ++++++++++++++++++
.../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 40 ++++
5 files changed, 400 insertions(+)
--
2.17.1
next reply other threads:[~2023-10-08 4:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 4:46 Keerthy [this message]
2023-10-08 4:46 ` [PATCH v8 1/7] arm64: dts: ti: k3-j721s2: Add ESM instances Keerthy
2023-10-08 4:46 ` [PATCH v8 2/7] arm64: dts: ti: k3-j784s4: " Keerthy
2023-10-08 4:46 ` [PATCH v8 3/7] arm64: dts: ti: k3-j7200: Add MCU domain ESM instance Keerthy
2023-10-08 4:46 ` [PATCH v8 4/7] arm64: dts: ti: k3-j784s4-main: Add the main domain watchdog instances Keerthy
2023-10-08 4:46 ` [PATCH v8 5/7] arm64: dts: ti: k3-j784s4-mcu: Add the mcu " Keerthy
2023-10-08 4:46 ` [PATCH v8 6/7] arm64: dts: ti: k3-j721s2-main: Add the main " Keerthy
2023-10-08 4:46 ` [PATCH v8 7/7] arm64: dts: ti: k3-j712s2-mcu: Add the mcu " Keerthy
2023-10-18 14:57 ` [PATCH v8 0/7] arm64: ti: k3-j7: Add the ESM & main domain watchdog nodes Vignesh Raghavendra
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=20231008044657.25788-1-j-keerthy@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=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;
as well as URLs for NNTP newsgroup(s).