From: robert.jarzmik@free•fr (Robert Jarzmik)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: xscale: correct auxiliary register in suspend/resume
Date: Thu, 27 Nov 2014 20:00:56 +0100 [thread overview]
Message-ID: <87vbm01n9z.fsf@free.fr> (raw)
In-Reply-To: <87r3wz6mvs.fsf@free.fr> (Robert Jarzmik's message of "Wed, 19 Nov 2014 19:55:35 +0100")
Robert Jarzmik <robert.jarzmik@free•fr> writes:
> Dmitry Eremin-Solenikov <dbaryshkov@gmail•com> writes:
> ...zip...
> Acked-by: Robert Jarzmik <robert.jarzmik@free•fr>
>
> Hi Russell,
>
> Is this patch in [1] fine by you so that Dmitry can submit it to your patch system ?
OK Dmitry, let's say that Russell didn't object. Please submit it to his patch
system (with the required procedure, kernel version upon which this applies, etc
... all in [2]).
If Russell disagrees, he'll drop the patch and you'll know there is more work.
Thanks.
--
Robert
[1] The patch
>
> ---8>---
> According to the manuals I have, XScale auxiliary register should be
> reached with opc_2 = 1 instead of crn = 1. cpu_xscale_proc_init
> correctly uses c1, c0, 1 arguments, but cpu_xscale_do_suspend and
> cpu_xscale_do_resume use c1, c1, 0. Correct suspend/resume functions to
> also use c1, c0, 1.
>
> The issue was primarily noticed thanks to qemu reporing "unsupported
> instruction" on the pxa suspend path. Confirmed in PXA210/250 and PXA255
> XScale Core manuals and in PXA270 and PXA320 Developers Guides.
>
> Harware tested by me on tosa (pxa255). Robert confirmed on pxa270 board.
>
> Tested-by: Robert Jarzmik <robert.jarzmik@free•fr>
> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail•com>
> ---
> arch/arm/mm/proc-xscale.S | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mm/proc-xscale.S b/arch/arm/mm/proc-xscale.S
> index 23259f1..afa2b3c 100644
> --- a/arch/arm/mm/proc-xscale.S
> +++ b/arch/arm/mm/proc-xscale.S
> @@ -535,7 +535,7 @@ ENTRY(cpu_xscale_do_suspend)
> mrc p15, 0, r5, c15, c1, 0 @ CP access reg
> mrc p15, 0, r6, c13, c0, 0 @ PID
> mrc p15, 0, r7, c3, c0, 0 @ domain ID
> - mrc p15, 0, r8, c1, c1, 0 @ auxiliary control reg
> + mrc p15, 0, r8, c1, c0, 1 @ auxiliary control reg
> mrc p15, 0, r9, c1, c0, 0 @ control reg
> bic r4, r4, #2 @ clear frequency change bit
> stmia r0, {r4 - r9} @ store cp regs
> @@ -552,7 +552,7 @@ ENTRY(cpu_xscale_do_resume)
> mcr p15, 0, r6, c13, c0, 0 @ PID
> mcr p15, 0, r7, c3, c0, 0 @ domain ID
> mcr p15, 0, r1, c2, c0, 0 @ translation table base addr
> - mcr p15, 0, r8, c1, c1, 0 @ auxiliary control reg
> + mcr p15, 0, r8, c1, c0, 1 @ auxiliary control reg
> mov r0, r9 @ control register
> b cpu_resume_mmu
> ENDPROC(cpu_xscale_do_resume)
[2] Russell's patch system rules
http://www.arm.linux.org.uk/developer/patches/info.php
next prev parent reply other threads:[~2014-11-27 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 12:05 [PATCH] ARM: xscale: correct auxiliary register in suspend/resume Dmitry Eremin-Solenikov
2014-11-19 18:55 ` Robert Jarzmik
2014-11-27 19:00 ` Robert Jarzmik [this message]
2014-11-27 19:17 ` Dmitry Eremin-Solenikov
-- strict thread matches above, loose matches on Subject: below --
2014-11-08 20:38 [PATCH] arm: " Dmitry Eremin-Solenikov
2014-11-09 15:23 ` Robert Jarzmik
2014-11-09 16:14 ` Dmitry Eremin-Solenikov
2014-11-09 18:04 ` Robert Jarzmik
2014-11-15 11:52 ` Robert Jarzmik
2014-11-15 12:06 ` Dmitry Eremin-Solenikov
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=87vbm01n9z.fsf@free.fr \
--to=robert.jarzmik@free$(echo .)fr \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox