diff options
| author | Tanmay Shah <tanmay.shah@amd.com> | 2026-05-27 08:16:11 +0300 |
|---|---|---|
| committer | Mathieu Poirier <mathieu.poirier@linaro.org> | 2026-05-29 18:02:33 +0300 |
| commit | a16272779b8a4194fd90c767ff1b347dcd55ddac (patch) | |
| tree | e39bc2072f5de6e144d1fe9c26b75c3ae38debb0 /include/linux/moduleloader.h | |
| parent | edfbf3a61b9f9defa337377e2904677a41edfbab (diff) | |
| download | linux-a16272779b8a4194fd90c767ff1b347dcd55ddac.tar.xz | |
remoteproc: xlnx: Enable auto boot feature
The remoteproc framework has capability to start (or attach to) the remote
processor automatically if auto boot flag is set by the driver during
probe. If the 'firmware-name' property is available for the remoteproc
node, then that firmware will be loaded and started during auto boot. If
the remote core is started by the bootloader then during auto-boot
remoteproc framework will try to attach to the remote processor.
The current architecture allocates and adds the remoteproc instance before
all the hardware such as sram, mbox, TCM is initialized. This design has
to be changed for auto boot to work. So, rename zynqmp_r5_rproc_add()
function to zynqmp_r5_rproc_alloc() and move adding the remoteproc
instance at the end of cluster initialization. This makes sure that all
the required hardware is initialized before starting the remote
processor.
Signed-off-by: Tanmay Shah <tanmay.shah@amd.com>
Link: https://lore.kernel.org/r/20260527051611.194844-3-tanmay.shah@amd.com
Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Diffstat (limited to 'include/linux/moduleloader.h')
0 files changed, 0 insertions, 0 deletions