From: Kevin Hilman <khilman@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP4: sleep: Save the complete used register stack frame
Date: Wed, 08 Aug 2012 10:15:20 -0700 [thread overview]
Message-ID: <87d331wbiv.fsf@ti.com> (raw)
In-Reply-To: <1342183715-13734-1-git-send-email-santosh.shilimkar@ti.com> (Santosh Shilimkar's message of "Fri, 13 Jul 2012 18:18:34 +0530")
Santosh Shilimkar <santosh.shilimkar@ti.com> writes:
> OMAP4 sleep entry code even though itself don't use many CPU registers
> makes call to the v7_flush_dcache_all() which uses them. Since
> v7_flush_dcache_all() doesn't make use of stack, the caller must take
> care of the stack frame. Otherwise it will lead to corrupted stack frame.
>
> Fix it by saving used registers.
>
> Reported-by: Grygorii Strashko <grygorii.strashko@ti.com>
> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Cc: Kevin Hilman <khilman@ti.com>
Please add a brief comment in the code as well explaining why the
additional registers are saved/restored.
After that, I'll add to my PM fixes queue for v3.6-rc.
Thanks for the fix.
Kevin
> ---
> arch/arm/mach-omap2/sleep44xx.S | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/sleep44xx.S b/arch/arm/mach-omap2/sleep44xx.S
> index 9f6b83d..b5823e9 100644
> --- a/arch/arm/mach-omap2/sleep44xx.S
> +++ b/arch/arm/mach-omap2/sleep44xx.S
> @@ -58,7 +58,7 @@ ppa_por_params:
> * CPU failed to transition to targeted OFF/DORMANT state.
> */
> ENTRY(omap4_finish_suspend)
> - stmfd sp!, {lr}
> + stmfd sp!, {r4-r12, lr}
> cmp r0, #0x0
> beq do_WFI @ No lowpower state, jump to WFI
>
> @@ -226,7 +226,7 @@ scu_gp_clear:
> skip_scu_gp_clear:
> isb
> dsb
> - ldmfd sp!, {pc}
> + ldmfd sp!, {r4-r12, pc}
> ENDPROC(omap4_finish_suspend)
>
> /*
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP4: sleep: Save the complete used register stack frame
Date: Wed, 08 Aug 2012 10:15:20 -0700 [thread overview]
Message-ID: <87d331wbiv.fsf@ti.com> (raw)
In-Reply-To: <1342183715-13734-1-git-send-email-santosh.shilimkar@ti.com> (Santosh Shilimkar's message of "Fri, 13 Jul 2012 18:18:34 +0530")
Santosh Shilimkar <santosh.shilimkar@ti.com> writes:
> OMAP4 sleep entry code even though itself don't use many CPU registers
> makes call to the v7_flush_dcache_all() which uses them. Since
> v7_flush_dcache_all() doesn't make use of stack, the caller must take
> care of the stack frame. Otherwise it will lead to corrupted stack frame.
>
> Fix it by saving used registers.
>
> Reported-by: Grygorii Strashko <grygorii.strashko@ti.com>
> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Cc: Kevin Hilman <khilman@ti.com>
Please add a brief comment in the code as well explaining why the
additional registers are saved/restored.
After that, I'll add to my PM fixes queue for v3.6-rc.
Thanks for the fix.
Kevin
> ---
> arch/arm/mach-omap2/sleep44xx.S | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/sleep44xx.S b/arch/arm/mach-omap2/sleep44xx.S
> index 9f6b83d..b5823e9 100644
> --- a/arch/arm/mach-omap2/sleep44xx.S
> +++ b/arch/arm/mach-omap2/sleep44xx.S
> @@ -58,7 +58,7 @@ ppa_por_params:
> * CPU failed to transition to targeted OFF/DORMANT state.
> */
> ENTRY(omap4_finish_suspend)
> - stmfd sp!, {lr}
> + stmfd sp!, {r4-r12, lr}
> cmp r0, #0x0
> beq do_WFI @ No lowpower state, jump to WFI
>
> @@ -226,7 +226,7 @@ scu_gp_clear:
> skip_scu_gp_clear:
> isb
> dsb
> - ldmfd sp!, {pc}
> + ldmfd sp!, {r4-r12, pc}
> ENDPROC(omap4_finish_suspend)
>
> /*
next prev parent reply other threads:[~2012-08-08 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 12:48 [PATCH] ARM: OMAP4: sleep: Save the complete used register stack frame Santosh Shilimkar
2012-07-13 12:48 ` Santosh Shilimkar
2012-08-08 17:15 ` Kevin Hilman [this message]
2012-08-08 17:15 ` Kevin Hilman
2012-08-09 5:51 ` Shilimkar, Santosh
2012-08-09 5:51 ` Shilimkar, Santosh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d331wbiv.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.