From: Hari Nagalla <hnagalla@ti.com>
To: <andersson@kernel.org>, <mathieu.poirier@linaro.org>,
<p.zabel@pengutronix.de>, <martyn.welch@collabora.com>,
<nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>
Cc: <linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>
Subject: [PATCH v5 0/5] TI K3 M4F support on AM64x and AM62x SoCs
Date: Mon, 7 Aug 2023 23:45:24 -0500 [thread overview]
Message-ID: <20230808044529.25925-1-hnagalla@ti.com> (raw)
The following series introduces K3 M4F remoteproc driver support for
AM64x and AM62x SoC families. These SoCs have a ARM Cortex M4F core in
the MCU voltage domain. For safety oriented applications, this core is
operated independently with out any IPC to other cores on the SoC.
However, for non safety applications, some customers use it as a remote
processor and so linux remote proc support is extended to the M4F core.
See AM64x Technical Reference Manual (SPRUIM2C – SEPTEMBER 2021) for
further details: https://www.ti.com/lit/pdf/SPRUIM2
Hari Nagalla (3):
dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs
arm64: dts: ti: k3-am62 : Add M4F remote proc node
arm64: dts: ti: k3-am64 : Add M4F remote proc node
Martyn Welch (2):
remoteproc: k3: Split out functions common with M4 driver
remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem
.../bindings/remoteproc/ti,k3-m4f-rproc.yaml | 136 ++++
arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 12 +
.../arm64/boot/dts/ti/k3-am62x-sk-common.dtsi | 19 +
arch/arm64/boot/dts/ti/k3-am64-mcu.dtsi | 12 +
arch/arm64/boot/dts/ti/k3-am642-evm.dts | 18 +
arch/arm64/boot/dts/ti/k3-am642-sk.dts | 18 +
drivers/remoteproc/Kconfig | 13 +
drivers/remoteproc/Makefile | 3 +-
drivers/remoteproc/ti_k3_common.c | 513 +++++++++++++++
drivers/remoteproc/ti_k3_common.h | 108 ++++
drivers/remoteproc/ti_k3_dsp_remoteproc.c | 598 +-----------------
drivers/remoteproc/ti_k3_m4_remoteproc.c | 333 ++++++++++
12 files changed, 1213 insertions(+), 570 deletions(-)
create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml
create mode 100644 drivers/remoteproc/ti_k3_common.c
create mode 100644 drivers/remoteproc/ti_k3_common.h
create mode 100644 drivers/remoteproc/ti_k3_m4_remoteproc.c
--
2.34.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-08-08 4:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 4:45 Hari Nagalla [this message]
2023-08-08 4:45 ` [PATCH v5 1/5] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs Hari Nagalla
2023-08-08 20:31 ` Rob Herring
2023-08-08 4:45 ` [PATCH v5 2/5] arm64: dts: ti: k3-am62 : Add M4F remote proc node Hari Nagalla
2023-08-08 12:07 ` Nishanth Menon
2023-08-08 4:45 ` [PATCH v5 3/5] arm64: dts: ti: k3-am64 " Hari Nagalla
2023-08-08 12:08 ` Nishanth Menon
2023-08-08 4:45 ` [PATCH v5 4/5] remoteproc: k3: Split out functions common with M4 driver Hari Nagalla
2023-08-29 19:47 ` Mathieu Poirier
2023-09-02 10:44 ` Hari Nagalla
2023-08-08 4:45 ` [PATCH v5 5/5] remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem Hari Nagalla
2023-08-29 20:01 ` Mathieu Poirier
2023-09-02 10:49 ` Hari Nagalla
2023-08-08 12:06 ` [PATCH v5 0/5] TI K3 M4F support on AM64x and AM62x SoCs 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=20230808044529.25925-1-hnagalla@ti.com \
--to=hnagalla@ti.com \
--cc=andersson@kernel.org \
--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=linux-remoteproc@vger.kernel.org \
--cc=martyn.welch@collabora.com \
--cc=mathieu.poirier@linaro.org \
--cc=nm@ti.com \
--cc=p.zabel@pengutronix.de \
--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