From 29913619c00f646195bf7eb412dc7c9ad6fe3896 Mon Sep 17 00:00:00 2001 From: Beleswar Padhi Date: Wed, 24 Dec 2025 16:28:32 +0530 Subject: [PATCH] PENDING: remoteproc: k3-r5: Fix order of suspend for cores in a R5 cluster Currently the driver suspends primary core followed by secondary core. However, R5Fs LPSC demands the primary core should always be at a higher power state than the secondary core. So, the secondary core should be powered off before primary core and vice-versa. Enforce this order during system suspend. Signed-off-by: Beleswar Padhi Reviewed-by: Udit Kumar Reviewed-by: Hari Nagalla --- drivers/remoteproc/ti_k3_r5_remoteproc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/remoteproc/ti_k3_r5_remoteproc.c b/drivers/remoteproc/ti_k3_r5_remoteproc.c index def6d69fee60..4242e78a47f1 100644 --- a/drivers/remoteproc/ti_k3_r5_remoteproc.c +++ b/drivers/remoteproc/ti_k3_r5_remoteproc.c @@ -629,7 +629,7 @@ static int k3_r5_suspend_late(struct device *dev) struct k3_r5_core *core; int ret = 0; - list_for_each_entry(core, &cluster->cores, elem) { + list_for_each_entry_reverse(core, &cluster->cores, elem) { struct k3_r5_rproc *kproc; struct rproc *rproc;