From: Andrew Davis <afd@ti.com>
To: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Hari Nagalla <hnagalla@ti.com>
Cc: <linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Andrew Davis <afd@ti.com>
Subject: [PATCH v10 0/8] TI K3 M4F support on AM62 and AM64 SoCs
Date: Mon, 10 Jun 2024 13:06:07 -0500 [thread overview]
Message-ID: <20240610180615.313622-1-afd@ti.com> (raw)
Hello all,
This is the continuation of the M4F RProc support series from here[0].
I'm helping out with the upstream task for Hari and so versions (v8+)
is a little different than the previous(v7-) postings[0]. Most notable
change I've introduced being the patches factoring out common support
from the current K3 R5 and DSP drivers have been dropped. I'd like
to do that re-factor *after* getting this driver in shape, that way
we have 3 similar drivers to factor out from vs trying to make those
changes in parallel with the series adding M4 support.
Anyway, details on our M4F subsystem can be found the
the AM62 TRM in the section on the same:
AM62x Technical Reference Manual (SPRUIV7A – MAY 2022)
https://www.ti.com/lit/pdf/SPRUIV7A
Thanks,
Andrew
[0] https://lore.kernel.org/linux-arm-kernel/20240202175538.1705-5-hnagalla@ti.com/T/
Changes for v10:
- Rebased on v6.10-rc3
- Added AM64 M4 support in DT
- Addressed comments by Mathieu from v9
Changes for v9:
- Fixed reserved-memory.yaml text in [1/5]
- Split dts patch into one for SoC and one for board enable
- Corrected DT property order and formatting [4/5][5/5]
Hari Nagalla (7):
dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs
arm64: dts: ti: k3-am62: Add M4F remoteproc node
arm64: dts: ti: k3-am625-sk: Add M4F remoteproc node
arm64: dts: ti: k3-am64: Add M4F remoteproc node
arm64: dts: ti: k3-am642-sk: Add M4F remoteproc node
arm64: dts: ti: k3-am642-evm: Add M4F remoteproc node
arm64: defconfig: Enable TI K3 M4 remoteproc driver
Martyn Welch (1):
remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem
.../bindings/remoteproc/ti,k3-m4f-rproc.yaml | 125 +++
arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 13 +
.../arm64/boot/dts/ti/k3-am62x-sk-common.dtsi | 19 +
arch/arm64/boot/dts/ti/k3-am64-mcu.dtsi | 13 +
arch/arm64/boot/dts/ti/k3-am642-evm.dts | 19 +
arch/arm64/boot/dts/ti/k3-am642-sk.dts | 19 +
arch/arm64/configs/defconfig | 1 +
drivers/remoteproc/Kconfig | 13 +
drivers/remoteproc/Makefile | 1 +
drivers/remoteproc/ti_k3_m4_remoteproc.c | 760 ++++++++++++++++++
10 files changed, 983 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml
create mode 100644 drivers/remoteproc/ti_k3_m4_remoteproc.c
--
2.39.2
next reply other threads:[~2024-06-10 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 18:06 Andrew Davis [this message]
2024-06-10 18:06 ` [PATCH v10 1/8] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs Andrew Davis
2024-06-10 18:06 ` [PATCH v10 2/8] remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem Andrew Davis
2024-06-18 17:05 ` Mathieu Poirier
2024-06-18 17:07 ` Andrew Davis
2024-06-10 18:06 ` [PATCH v10 3/8] arm64: dts: ti: k3-am62: Add M4F remoteproc node Andrew Davis
2024-06-10 18:06 ` [PATCH v10 4/8] arm64: dts: ti: k3-am625-sk: " Andrew Davis
2024-06-10 18:06 ` [PATCH v10 5/8] arm64: dts: ti: k3-am64: " Andrew Davis
2024-06-10 18:06 ` [PATCH v10 6/8] arm64: dts: ti: k3-am642-sk: " Andrew Davis
2024-06-10 18:06 ` [PATCH v10 7/8] arm64: dts: ti: k3-am642-evm: " Andrew Davis
2024-06-10 18:06 ` [PATCH v10 8/8] arm64: defconfig: Enable TI K3 M4 remoteproc driver Andrew Davis
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=20240610180615.313622-1-afd@ti.com \
--to=afd@ti.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@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=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=nm@ti.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).