| Message ID | 20240618184636.30642-1-hnagalla@ti.com |
|---|---|
| Headers | show |
| Series | Add M4 remoteproc driver for TI K3 SoCs | expand |
On 13:46-20240618, Hari Nagalla wrote: > This series adds support for M4 remoteproc driver for K3 devices. > > Logs: https://paste.sr.ht/~hnagalla/62811c4003c27ada83bc1c94500f7714ab30092a Obviously - this cannot work with out an M4F node in dts, correct? you should have mentioned that in your email. > > Hari Nagalla (3): > remoteproc: k3-m4: Introduce K3 remote proc driver for M4 subsystem > configs: am62x_evm_a53_defconfig: Enable M4 remote proc driver > board: ti: am62x: Add remote proc env variables > > board/ti/am62x/am62x.env | 4 + > configs/am62x_evm_a53_defconfig | 2 + > drivers/remoteproc/Kconfig | 10 + > drivers/remoteproc/Makefile | 1 + > drivers/remoteproc/ti_k3_m4_rproc.c | 421 ++++++++++++++++++++++++++++ > 5 files changed, 438 insertions(+) > create mode 100644 drivers/remoteproc/ti_k3_m4_rproc.c > > -- > 2.34.1 > I know we are close[1], but do wait for upstream kernel to accept the bindings before using the same in driver etc. the dts has no m4 support atm. [1] https://lore.kernel.org/r/33550e82-4fd3-4066-b78d-27534584fa5b@ti.com
On 6/18/24 13:54, Nishanth Menon wrote: > On 13:46-20240618, Hari Nagalla wrote: >> This series adds support for M4 remoteproc driver for K3 devices. >> >> Logs:https://paste.sr.ht/~hnagalla/62811c4003c27ada83bc1c94500f7714ab30092a > Obviously - this cannot work with out an M4F node in dts, correct? you > should have mentioned that in your email. > Yes, that is correct. It needs M4F node in dts. I should have mentioned it in the email, that the kernel to u-boot device tree sync is needed for it to work.