From: Beleswar Padhi <b-padhi@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>
Cc: <kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<vaishnav.a@ti.com>, <j-choudhary@ti.com>, <u-kumar1@ti.com>
Subject: [PATCH 0/3] Add Remoteproc Support for TI's J722S SoCs
Date: Fri, 7 Jun 2024 14:34:30 +0530 [thread overview]
Message-ID: <20240607090433.488454-1-b-padhi@ti.com> (raw)
Hello All,
The K3 J722S SoCs have one single-core Arm Cortex-R5F processor in each
of the WAKEUP, MCU and MAIN voltage domain, and two C71x DSP subsystems
in MAIN voltage domain. Thus, Add the DT Nodes and memory carveout
regions to add remoteproc support in J722S SoCs.
Apurva Nandan (2):
arm64: dts: ti: Add R5F and C7x remote processor nodes
arm64: dts: ti: k3-j722s-evm: Add memory carveouts for R5F and C7x
Beleswar Padhi (1):
arm64: dts: ti: k3-j722s-evm: Enable Mailbox clusters
arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 140 ++++++++++++++++++++++++
arch/arm64/boot/dts/ti/k3-j722s.dtsi | 63 +++++++++++
2 files changed, 203 insertions(+)
--
2.34.1
next reply other threads:[~2024-06-07 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 9:04 Beleswar Padhi [this message]
2024-06-07 9:04 ` [PATCH 1/3] arm64: dts: ti: Add R5F and C7x remote processor nodes Beleswar Padhi
2024-06-07 13:50 ` Andrew Davis
2024-06-08 12:59 ` kernel test robot
2024-06-11 7:35 ` kernel test robot
2024-06-07 9:04 ` [PATCH 2/3] arm64: dts: ti: k3-j722s-evm: Enable Mailbox clusters Beleswar Padhi
2024-06-07 9:04 ` [PATCH 3/3] arm64: dts: ti: k3-j722s-evm: Add memory carveouts for R5F and C7x Beleswar Padhi
2024-06-07 13:53 ` Andrew Davis
2024-06-07 14:25 ` [PATCH 0/3] Add Remoteproc Support for TI's J722S SoCs Rob Herring (Arm)
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=20240607090433.488454-1-b-padhi@ti.com \
--to=b-padhi@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-choudhary@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vaishnav.a@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
all inboxes | Powered by JetHome®