summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-s5p64x0
diff options
context:
space:
mode:
authorAbhilash Kesavan <a.kesavan@samsung.com>2013-01-25 10:40:19 -0800
committerKukjin Kim <kgene.kim@samsung.com>2013-01-30 22:28:05 -0800
commitd3fcacf52d24ff1b12d994d9ddb7496f651294a2 (patch)
tree551b22ecd840f7ad76d0f057de2db1d1c8be1437 /arch/arm/mach-s5p64x0
parent8baaa265c5e8e378cb60164f47e24bf296a6d685 (diff)
downloadlinux-d3fcacf52d24ff1b12d994d9ddb7496f651294a2.tar.gz
linux-d3fcacf52d24ff1b12d994d9ddb7496f651294a2.tar.bz2
linux-d3fcacf52d24ff1b12d994d9ddb7496f651294a2.zip
ARM: SAMSUNG: Gracefully exit on suspend failure
As per the Exynos5250 User Manual: When there are pending interrupt events, WFI/WFE instruction are ignored. To cancel the power-down sequence follow these steps: 1) Disable system power-down using CENTRAL_SEQ_CONFIGURATION register 2) Clear WAKEUP_STAT register 3) Enable interrupt service routine for CPU Code for early wakeup for exynos already exists. Remove the panic on suspend failure, clear the wakeup state register and return 1 from cpu_suspend to indicate a failed suspend (to a user daemon). Older Samsung SoCs have similar panics and I have removed them all. Haven't touched the S3C2410 sleep code. Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
Diffstat (limited to 'arch/arm/mach-s5p64x0')
-rw-r--r--arch/arm/mach-s5p64x0/pm.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/arch/arm/mach-s5p64x0/pm.c b/arch/arm/mach-s5p64x0/pm.c
index 9cba18bfe47b..97c2a08ad490 100644
--- a/arch/arm/mach-s5p64x0/pm.c
+++ b/arch/arm/mach-s5p64x0/pm.c
@@ -103,8 +103,8 @@ static int s5p64x0_cpu_suspend(unsigned long arg)
"mcr p15, 0, %0, c7, c10, 4\n\t"
"mcr p15, 0, %0, c7, c0, 4" : : "r" (tmp));
- /* we should never get past here */
- panic("sleep resumed to originator?");
+ pr_info("Failed to suspend the system\n");
+ return 1; /* Aborting suspend */
}
/* mapping of interrupts to parts of the wakeup mask */