remoteproc: zynqmp_r5: initialize IPI before start R5

The remoteproc driver should initialize IPI before it starts R5
because as long as R5 boots, it can kick APU.

Signed-off-by: Wendy Liang <jliang@xilinx.com>
Signed-off-by: Michal Simek <michal.simek@xilinx.com>

diff --git a/drivers/remoteproc/zynqmp_r5_remoteproc.c b/drivers/remoteproc/zynqmp_r5_remoteproc.c
index ce9176d27fd34c892346fd5cc00ba3b5d9c2f9d3..606422162987e755f7ef3f0ef16fa858b26874a0 100644 (file)
--- a/drivers/remoteproc/zynqmp_r5_remoteproc.c
+++ b/drivers/remoteproc/zynqmp_r5_remoteproc.c
@@ -313,6 +313,7 @@ static int zynqmp_r5_rproc_start(struct rproc *rproc)
        dev_info(dev, "RPU boot from %s.",
                local->bootmem == OCM ? "OCM" : "TCM");
 
+       ipi_init(local);
        r5_mode_config(local);
        r5_halt(local, true);
        r5_reset(local, true);
@@ -322,7 +323,6 @@ static int zynqmp_r5_rproc_start(struct rproc *rproc)
        r5_reset(local, false);
        r5_halt(local, false);
 
-       ipi_init(local);
        return 0;
 }