diff options
| author | Tom Rini <trini@konsulko.com> | 2025-10-24 12:09:02 -0600 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2025-10-24 13:47:50 -0600 |
| commit | fd976ff3a233ae7c6a9f5bec790b02bbbf57bb24 (patch) | |
| tree | 1bffd9388bcc9856cb9451c2034ef18158f356b3 /arch/arm/mach-zynqmp | |
| parent | fae6c54d238279bf79c66ca65330425dff2c952f (diff) | |
| parent | ac9b02dd1028d14b6326970c93dfc3c50daa16f1 (diff) | |
Peng Fan (OSS) <peng.fan@oss.nxp.com> says:
i.MX95 System Manager(SM) implements Logical Machine Management(LMM) and
CPU protocol to manage Logical Machine(LM) and CPUs(eg, M7).
To manage M7 in a separate LM or in same LM as U-Boot/Linux itself. LMM
APIs and CPU APIs are needed.
When M7 is in LM 'lm-m7', and this LM is managable by 'uboot-lm', U-Boot
could use LMM_BOOT, LMM_SHUTDOWN and etc to manage 'lm-m7'.
If in same LM, use CPU_START, CPU_STOP, CPU_RESET_VECTOR_SET and etc to
manage M7.
Both LMM/CPU APIs will be used by remoteproc driver.
The documentation could be found in Linux Kernel:
drivers/firmware/arm_scmi/vendors/imx/imx95.rst
Link: https://lore.kernel.org/r/20251017-scmi-lmm-v1-0-9fd41e7a5ac0@nxp.com
Diffstat (limited to 'arch/arm/mach-zynqmp')
0 files changed, 0 insertions, 0 deletions