From: Beleswar Padhi <b-padhi@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <u-kumar1@ti.com>, <j-choudhary@ti.com>, <vaishnav.a@ti.com>,
<afd@ti.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v4 0/2] Add Remoteproc Support for TI's J722S SoCs
Date: Thu, 29 Aug 2024 11:39:30 +0530 [thread overview]
Message-ID: <20240829060932.3441295-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, this series adds the DT Nodes for the
remote processors to add support for IPC.
This series also enables IPC on the J722S-EVM platform based on the
above SoC by adding the mailbox instances, shared memory carveouts and
reserving the conflicting timer nodes (as they are used by remoteproc
firmware).
v4: Changelog:
* Nishanth:
1) Fixed DT node properties order to put standard properties before vendor
specific properties in patch "arm64: dts: ti: k3-j722s-main: Add R5F
and C7x remote processor nodes"
2) Put "status" property at the end in extended DT nodes and preceded
child nodes with a single blank line wherever applicable in patch
"arm64: dts: ti: k3-j722s-evm: Enable Inter-Processor Communication"
following kernel DTS coding style.
Link to v3:
https://lore.kernel.org/all/20240828112713.2668526-1-b-padhi@ti.com/
v3: Changelog:
1) Reserved conflicting Timer Nodes in k3-j722s-evm.dts file to avoid remotecore
boot failures.
Link to v2:
https://lore.kernel.org/all/20240612112259.1131653-1-b-padhi@ti.com/
v2: Changelog:
1) Addressed Andrew's comments to refactor remotecore nodes into
k3-j722s-main.dtsi file.
2) Squashed Patch 2 and 3 from V1 into Patch 2 in V2 as they were doing
the same logical thing.
3) The DTBs check warnings from V1 are automatically fixed after a
dt-binding patch[0] was merged in linux-next.
Link to v1:
https://lore.kernel.org/all/20240607090433.488454-1-b-padhi@ti.com/
[0]: https://lore.kernel.org/all/20240604171450.2455-1-hnagalla@ti.com/
Apurva Nandan (2):
arm64: dts: ti: k3-j722s-main: Add R5F and C7x remote processor nodes
arm64: dts: ti: k3-j722s-evm: Enable Inter-Processor Communication
arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 157 ++++++++++++++++++++++
arch/arm64/boot/dts/ti/k3-j722s-main.dtsi | 61 +++++++++
2 files changed, 218 insertions(+)
--
2.34.1
next reply other threads:[~2024-08-29 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 6:09 Beleswar Padhi [this message]
2024-08-29 6:09 ` [PATCH v4 1/2] arm64: dts: ti: k3-j722s-main: Add R5F and C7x remote processor nodes Beleswar Padhi
2024-08-30 15:10 ` Kumar, Udit
2024-08-30 15:21 ` Andrew Davis
2024-08-29 6:09 ` [PATCH v4 2/2] arm64: dts: ti: k3-j722s-evm: Enable Inter-Processor Communication Beleswar Padhi
2024-08-30 13:57 ` Kumar, Udit
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=20240829060932.3441295-1-b-padhi@ti.com \
--to=b-padhi@ti.com \
--cc=afd@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;
as well as URLs for NNTP newsgroup(s).