| Message ID | 20241003170118.24932-1-afd@ti.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | TI K3 M4F support on AM62 and AM64 SoCs | expand |
Hi Andrew Davis, On Thu, 03 Oct 2024 12:01:13 -0500, Andrew Davis wrote: > 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 > > [...] I have applied the following to branch ti-k3-dts-next on [1]. Thank you! [1/5] arm64: dts: ti: k3-am62: Add M4F remoteproc node commit: be4bac3bcb281b264bd35ae1ff7bbbb99e3e00fe [2/5] arm64: dts: ti: k3-am625-sk: Add M4F remoteproc node commit: 23a6aba92e53883bccbbb27933aad6dd09992e6f [3/5] arm64: dts: ti: k3-am64: Add M4F remoteproc node commit: ef1876ff76096b3cad6fdb8b797226e4914f5726 [4/5] arm64: dts: ti: k3-am642-sk: Add M4F remoteproc node commit: 6e36e6200360e1703071b38fa5e91f4894716658 [5/5] arm64: dts: ti: k3-am642-evm: Add M4F remoteproc node commit: 8e77fc1fbb291e193664df0ac5176ac9fbfb3ea8 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. [1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git -- Vignesh
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@ti.com/ 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(+)