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 <b-padhi@ti.com> Reviewed-by: Udit Kumar <u-kumar1@ti.com> Reviewed-by: Hari Nagalla <hnagalla@ti.com>
This commit is contained in:
committed by
Udit Kumar
parent
441aa9b97a
commit
29913619c0
@@ -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;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user