[PATCH v11 0/9] TI K3 M4F support on AM62 and AM64 SoCs

Andrew Davis posted 9 patches 1 year, 4 months ago
There is a newer version of this series
.../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_dsp_remoteproc.c     |  28 +-
drivers/remoteproc/ti_k3_m4_remoteproc.c      | 667 ++++++++++++++++++
drivers/remoteproc/ti_k3_r5_remoteproc.c      |  28 +-
drivers/remoteproc/ti_sci_proc.h              |  26 +
13 files changed, 918 insertions(+), 54 deletions(-)
create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml
create mode 100644 drivers/remoteproc/ti_k3_m4_remoteproc.c
[PATCH v11 0/9] TI K3 M4F support on AM62 and AM64 SoCs
Posted by Andrew Davis 1 year, 4 months ago
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 v11:
 - Added patch [2/9] factoring out a common function
 - Addressed comments by Mathieu from v10
 - Rebased on v6.11-rc1
 - Small reworks in driver for readability

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]

Andrew Davis (1):
  remoteproc: k3: Factor out TI-SCI processor control OF get function

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_dsp_remoteproc.c     |  28 +-
 drivers/remoteproc/ti_k3_m4_remoteproc.c      | 667 ++++++++++++++++++
 drivers/remoteproc/ti_k3_r5_remoteproc.c      |  28 +-
 drivers/remoteproc/ti_sci_proc.h              |  26 +
 13 files changed, 918 insertions(+), 54 deletions(-)
 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

Re: [PATCH v11 0/9] TI K3 M4F support on AM62 and AM64 SoCs
Posted by Wadim Egorov 1 year, 4 months ago

Am 02.08.24 um 17:21 schrieb Andrew Davis:
> 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 v11:
>   - Added patch [2/9] factoring out a common function
>   - Addressed comments by Mathieu from v10
>   - Rebased on v6.11-rc1
>   - Small reworks in driver for readability

Tested on a AM62x & AM64x using phycore-am62x & phycore-am64x, so

Tested-by: Wadim Egorov <w.egorov@phytec.de>

> 
> 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]
> 
> Andrew Davis (1):
>    remoteproc: k3: Factor out TI-SCI processor control OF get function
> 
> 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_dsp_remoteproc.c     |  28 +-
>   drivers/remoteproc/ti_k3_m4_remoteproc.c      | 667 ++++++++++++++++++
>   drivers/remoteproc/ti_k3_r5_remoteproc.c      |  28 +-
>   drivers/remoteproc/ti_sci_proc.h              |  26 +
>   13 files changed, 918 insertions(+), 54 deletions(-)
>   create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml
>   create mode 100644 drivers/remoteproc/ti_k3_m4_remoteproc.c
> 

Re: (subset) [PATCH v11 0/9] TI K3 M4F support on AM62 and AM64 SoCs
Posted by Nishanth Menon 11 months, 2 weeks ago
Hi Andrew Davis,

On Fri, 02 Aug 2024 10:21:00 -0500, Andrew Davis wrote:
> 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.
> 
> [...]

I have applied the following to branch ti-k3-config-next on [1].
Thank you!

[9/9] arm64: defconfig: Enable TI K3 M4 remoteproc driver
      commit: 184caba444cfd4b90231de7d071b9966c115c29f

Thanks for the headsup Daniel.

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
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D