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: Sun, 09 Nov 2014 16:23:19 +0100 [thread overview]
Message-ID: <87oasgv1nc.fsf@free.fr> (raw)
In-Reply-To: 1415479134-19999-1-git-send-email-dbaryshkov@gmail.com
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> writes:
> 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.
> - mrc p15, 0, r8, c1, c1, 0 @ auxiliary control reg
> + mrc p15, 0, r8, c1, c0, 1 @ auxiliary control reg
My PXA320 manual says (PXA320 Developer's Guide, chapter 2.16.1, table 5) :
- Auxiliary Register: Crn=1, Crm=0, Opcode1=0, Opcode2=1
=> that is what your patch changes
My PXA270 manual says (PXA270 Developer's Guide, chapter 2.2.5.3) :
- Auxiliary Register: Crn=1, Crm=<don't care>, Opcode1=0, Opcode2=1
=> same story as for the PX320
My PXA255 manual doesn't say anything, but the Intel XScale Core Architecture
manual seems to be applicable to it, and gives you reason.
Moreover the CP15, Opcode=1, Crn=1, Crm=0, Opcode2=* doesn't point to any valid
register in XScale architecture AFAIK.
So your patch looks correct to me. I have a couple of questions :
- did you see an incorrect behaviour without your patch or is this coming from
code inspection ?
- did you test this patch during a suspend/resume cycle, and if so on which
variants (pxa25x and tosa maybe) ?
As you might haved guessed, I'd like all these questions to have an answer in
the commit message.
Cheers.
--
Robert
next prev parent reply other threads:[~2014-11-09 15:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 20:38 [PATCH] arm: xscale: correct auxiliary register in suspend/resume Dmitry Eremin-Solenikov
2014-11-09 15:23 ` Robert Jarzmik [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2014-11-15 12:05 [PATCH] ARM: " Dmitry Eremin-Solenikov
2014-11-19 18:55 ` Robert Jarzmik
2014-11-27 19:00 ` Robert Jarzmik
2014-11-27 19:17 ` 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=87oasgv1nc.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=linux-arm-kernel@lists.infradead.org \
/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.