Commit fff94cd9 authored by Ben Dooks's avatar Ben Dooks

[ARM] S3C: Tidy sleep code path to fix call flow

As noted by Russell King, the sleep code path is not
elegant and makes use of leaving items on the stack
between calls.

Change the code that does the following:

        if (s3c_cpu_save(regs_save) == 0) {
                flush_cache_all();
                S3C_PMDBG("preparing to sleep\n");
                pm_cpu_sleep();
        }

to simply call s3c_cpu_save, and let that do the
necessary calls to quiesce and sleep the system.
Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
parent aa8aba69
...@@ -162,5 +162,13 @@ extern void s3c_pm_restore_gpios(void); ...@@ -162,5 +162,13 @@ extern void s3c_pm_restore_gpios(void);
*/ */
extern void s3c_pm_save_gpios(void); extern void s3c_pm_save_gpios(void);
/**
* s3c_pm_cb_flushcache - callback for assembly code
*
* Callback to issue flush_cache_all() as this call is
* not a directly callable object.
*/
extern void s3c_pm_cb_flushcache(void);
extern void s3c_pm_save_core(void); extern void s3c_pm_save_core(void);
extern void s3c_pm_restore_core(void); extern void s3c_pm_restore_core(void);
...@@ -229,7 +229,7 @@ void (*pm_cpu_sleep)(void); ...@@ -229,7 +229,7 @@ void (*pm_cpu_sleep)(void);
static int s3c_pm_enter(suspend_state_t state) static int s3c_pm_enter(suspend_state_t state)
{ {
unsigned long regs_save[16]; static unsigned long regs_save[16];
/* ensure the debug is initialised (if enabled) */ /* ensure the debug is initialised (if enabled) */
...@@ -289,15 +289,11 @@ static int s3c_pm_enter(suspend_state_t state) ...@@ -289,15 +289,11 @@ static int s3c_pm_enter(suspend_state_t state)
s3c_pm_arch_stop_clocks(); s3c_pm_arch_stop_clocks();
/* s3c2410_cpu_save will also act as our return point from when /* s3c_cpu_save will also act as our return point from when
* we resume as it saves its own register state, so use the return * we resume as it saves its own register state and restores it
* code to differentiate return from save and return from sleep */ * during the resume. */
if (s3c_cpu_save(regs_save) == 0) { s3c_cpu_save(regs_save);
flush_cache_all();
S3C_PMDBG("preparing to sleep\n");
pm_cpu_sleep();
}
/* restore the cpu state using the kernel's cpu init code. */ /* restore the cpu state using the kernel's cpu init code. */
...@@ -325,6 +321,12 @@ static int s3c_pm_enter(suspend_state_t state) ...@@ -325,6 +321,12 @@ static int s3c_pm_enter(suspend_state_t state)
return 0; return 0;
} }
/* callback from assembly code */
void s3c_pm_cb_flushcache(void)
{
flush_cache_all();
}
static int s3c_pm_prepare(void) static int s3c_pm_prepare(void)
{ {
/* prepare check area if configured */ /* prepare check area if configured */
......
...@@ -42,21 +42,9 @@ ...@@ -42,21 +42,9 @@
.text .text
/* s3c_cpu_save /* s3c_cpu_save
*
* save enough of the CPU state to allow us to re-start
* pm.c code. as we store items like the sp/lr, we will
* end up returning from this function when the cpu resumes
* so the return value is set to mark this.
*
* This arangement means we avoid having to flush the cache
* from this code.
* *
* entry: * entry:
* r0 = pointer to save block * r0 = save address (virtual addr of s3c_sleep_save_phys)
*
* exit:
* r0 = 0 => we stored everything
* 1 => resumed from sleep
*/ */
ENTRY(s3c_cpu_save) ENTRY(s3c_cpu_save)
...@@ -71,14 +59,19 @@ ENTRY(s3c_cpu_save) ...@@ -71,14 +59,19 @@ ENTRY(s3c_cpu_save)
stmia r0, { r4 - r13 } stmia r0, { r4 - r13 }
mov r0, #0 @@ write our state back to RAM
ldmfd sp, { r4 - r12, pc } bl s3c_pm_cb_flushcache
@@ jump to final code to send system to sleep
ldr r0, =pm_cpu_sleep
@@ldr pc, [ r0 ]
ldr r0, [ r0 ]
mov pc, r0
@@ return to the caller, after having the MMU @@ return to the caller, after having the MMU
@@ turned on, this restores the last bits from the @@ turned on, this restores the last bits from the
@@ stack @@ stack
resume_with_mmu: resume_with_mmu:
mov r0, #1
ldmfd sp!, { r4 - r12, pc } ldmfd sp!, { r4 - r12, pc }
.ltorg .ltorg
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment