i.MX95 features a Cortex-M33 core, six Cortex-A55 cores, and
one Cortex-M7 core. The System Control Management Interface(SCMI)
firmware runs on the M33 core. The i.MX95 SCMI firmware named System
Manager(SM) includes vendor extension protocols, Logical Machine
Management(LMM) protocol and CPU protocol and etc.
There are three cases for M7:
(1) M7 in a separate Logical Machine(LM) that Linux couldn't control it.
(2) M7 in a separate Logical Machine that Linux could control it using
LMM protocol
(3) M7 runs in same Logical Machine as A55, so Linux could control it
using CPU protocol
In patch 2, Use LMM and CPU protocol to manage M7. More info could be
found in the patch commit log
Current setup relies on pre-Linux software(U-Boot) to do
M7 TCM ECC initialization. In future, we could add the support in Linux
to decouple U-Boot and Linux.
Patchset was tested with below boot images when the patchset based on
next-20250526:
imx-boot-variant-rpmsg-imx95-19x19-lpddr5-evk-sd.bin-flash_lpboot_sm_a55 (Use
LMM protocol)
imx-boot-variant-alt-imx95-19x19-lpddr5-evk-sd.bin-flash_alt (Use CPU protocol)
imx-boot-imx95-19x19-lpddr5-evk-sd.bin-flash_a55 (M7 not under A55 control)
imx-boot-imx95-19x19-lpddr5-evk-sd.bin-flash_all (M7 not under A55 control)
Patchset was tested again with rebase on next-20250623
Patchset was tested again with rebase on next-20250710
Patchset is re-based on next-20250603.
Thanks for Daniel/Frank helping review the patchset before posting out to list.
Signed-off-by: Peng Fan <peng....@nxp.com>
---
Changes in v5:
- Rebased to next-20250820 to resolve minor conflict in patch 2, as below
if (dcfg->method == IMX_RPROC_NONE || dcfg->method == IMX_RPROC_SCU_API)
=>
if (dcfg->method == IMX_RPROC_NONE || dcfg->method == IMX_RPROC_SCU_API ||
dcfg->method == IMX_RPROC_SM)
- Add Kconfig denpendencies in patch 2 following 514b2262ade4 ("firmware:
arm_scmi: Fix i.MX build dependency")
- Drop patch 4,5 which are dts changes that enable cm7 node for i.MX95, but
there are dtbs_check error because of "linux,code" property not laned in
tree. To avoid false alarm on this patchset, so drop the two patches.
- Link to v4:
https://lore.kernel.org/r/20250710-imx95-rproc-1-v4-0-a7123e857...@nxp.com
Changes in v4:
- Move the lmm permission check code to a separate
function(imx_rproc_sm_lmm_prepare) in patch 3.
- Check return value of scmi_imx_cpu_started in patch 3
- Rebased to next-20250710 and tested on i.MX95-19x19-EVK
- Add R-b from Frank for patch 1-4 and A-b from Krzysztof for patch 1
- Drop mu7 from patch 5, because mu7 status was already okay.
- Link to v3:
https://lore.kernel.org/r/20250625-imx95-rproc-1-v3-0-699031f59...@nxp.com
Changes in v3:
- Drop fsl,lmm-id and fsl,cpu-id for binding in patch 1
- Add lmid and cpuid in driver patch 2.
- Add i.MX95 lmid and cpuid in patch 3
- Rebased to linux-next-6-23 and tested with this new rebased version
- Add dtsi/dts patch 4,5 to give people a view on how it is used per Krzysztof
- Daniel's R-b are still kept after talk with Daniel
- Link to v2:
https://lore.kernel.org/r/20250606-imx95-rproc-1-v2-0-a2bd64438...@nxp.com
Changes in v2:
- Typo fix in patch 2 commit message
- Move the m7 address mapping array from patch 2 to patch 3
- Add R-b from Daniel to patch 3
- Link to v1:
https://lore.kernel.org/r/20250604-imx95-rproc-1-v1-0-a6e5f5127...@nxp.com
---
Peng Fan (3):
dt-bindings: remoteproc: fsl,imx-rproc: Add support for i.MX95
remoteproc: imx_rproc: Add support for System Manager API
remoteproc: imx_rproc: Add support for i.MX95
.../bindings/remoteproc/fsl,imx-rproc.yaml | 1 +
drivers/remoteproc/Kconfig | 2 +
drivers/remoteproc/imx_rproc.c | 148 ++++++++++++++++++++-
drivers/remoteproc/imx_rproc.h | 5 +
4 files changed, 153 insertions(+), 3 deletions(-)
---
base-commit: c4b125bd6408789809eb57701eabb4cdc6407d75
change-id: 20250525-imx95-rproc-1-20bb74ddc8af
Best regards,
--
Peng Fan <peng....@nxp.com>
