Hello all,
M4F driver[0] and DT bindings[1] are in, so last step is adding the
nodes to the base AM64/AM62 DTSI files, plus a couple of our
SK boards. These can be used as a reference for other boards using
AM64/AM62, or I can add these nodes for existing upstream boards,
just let me know.
Thanks,
Andrew
[0] commit ebcf9008a895a ("remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem")
[1] commit 9fedb829372d4 ("dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs")
Changes for v12:
- Rebased on v6.12-rc1
- Dropped taken patches
- Added Tested-by tags
Previous series (v11):
https://lore.kernel.org/linux-arm-kernel/20240802152109.137243-1-afd@xxxxxx/
Hari Nagalla (5):
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
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 +++++++++++++++++++
5 files changed, 83 insertions(+)
--
2.39.2
