From: Hari Nagalla <hnagalla@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>
Cc: <kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/2] Add R5F and C71 DSP nodes for J784S4 SoC
Date: Thu, 30 Mar 2023 09:15:34 -0500 [thread overview]
Message-ID: <20230330141536.22480-1-hnagalla@ti.com> (raw)
This series adds the R5F cluster and C71 DSP processor nodes for
J784S4 SoC.
The first patch adds R5F cluster nodes to the MAIN and MCU voltage
domains of J784S4 SoC. The second patch adds the C71 DSP processor
nodes to the MAIN voltage domain of J784S4 SoC.
Changes in V2:
- Removed default disable of R5F nodes in the SoC device tree.
- Consolidated R5F nodes into one patch.
V1: https://lore.kernel.org/all/20230329093627.30719-1-hnagalla@ti.com/
Hari Nagalla (2):
arm64: dts: ti: k3-j784s4-main: Add R5F cluster nodes
arm64: dts: ti: k3-j784s4-main: Add C71x DSP nodes
arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 168 ++++++++++++++++++
.../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 40 +++++
2 files changed, 208 insertions(+)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-03-30 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 14:15 Hari Nagalla [this message]
2023-03-30 14:15 ` [PATCH v2 1/2] arm64: dts: ti: k3-j784s4-main: Add R5F cluster nodes Hari Nagalla
2023-03-30 14:15 ` [PATCH v2 2/2] arm64: dts: ti: k3-j784s4-main: Add C71x DSP nodes Hari Nagalla
2023-03-30 14:55 ` [PATCH v2 0/2] Add R5F and C71 DSP nodes for J784S4 SoC Nishanth Menon
2023-03-31 9:31 ` Hari Nagalla
2023-03-31 15:51 ` Nishanth Menon
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=20230330141536.22480-1-hnagalla@ti.com \
--to=hnagalla@ti.com \
--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