diff options
| author | Venkatesh Yadav Abbarapu | 2023-06-08 08:51:52 +0530 |
|---|---|---|
| committer | Michal Simek | 2023-06-12 13:25:02 +0200 |
| commit | a30ac34ca8967cb318d4a435258dea78242d9d45 (patch) | |
| tree | 2349707627f12d22332bb6f4a187de8c37b4e7dc /arch | |
| parent | 2eed42c2f18c739303b098370019e366aeb64ae6 (diff) | |
arm64: zynqmp: Fix lockstep mode cpu release functionality
For lockstep mode, cpu_release function is expecting to execute
on R5 core 0, if there is attempt to pass other than R5 core 0,
through an error saying "Lockstep mode should run on R5 core 0 only".
Signed-off-by: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>
Link: https://lore.kernel.org/r/20230608032152.980-3-venkatesh.abbarapu@amd.com
Signed-off-by: Michal Simek <michal.simek@amd.com>
Diffstat (limited to 'arch')
| -rw-r--r-- | arch/arm/mach-zynqmp/mp.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/arch/arm/mach-zynqmp/mp.c b/arch/arm/mach-zynqmp/mp.c index 7a12f4b2b6c..b06c867e57f 100644 --- a/arch/arm/mach-zynqmp/mp.c +++ b/arch/arm/mach-zynqmp/mp.c @@ -326,6 +326,10 @@ int cpu_release(u32 nr, int argc, char *const argv[]) flush_dcache_all(); if (!strncmp(argv[1], "lockstep", 8)) { + if (nr != ZYNQMP_CORE_RPU0) { + printf("Lockstep mode should run on ZYNQMP_CORE_RPU0\n"); + return 1; + } printf("R5 lockstep mode\n"); set_r5_reset(nr, LOCK); set_r5_tcm_mode(LOCK); |