From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: save/restore diagnostic register on ARMv7 suspend/resume
Date: Wed, 18 Jun 2014 20:39:08 +0800 [thread overview]
Message-ID: <20140618123906.GI8860@dragon> (raw)
In-Reply-To: <20140618104009.GH32699@arm.com>
On Wed, Jun 18, 2014 at 11:40:09AM +0100, Will Deacon wrote:
> On Wed, Jun 18, 2014 at 09:49:58AM +0100, Shawn Guo wrote:
> > The CP15 diagnostic register holds ARM errata bits on ARMv7, so it
> > needs to be saved/restored on suspend/resume. Otherwise, the
> > effectiveness of errata workaround gets lost together with diagnostic
> > register bit across suspend/resume cycle.
>
> This should be conditional on Cortex-A9, since this register is certainly
> not architected.
Ah, yes. In that case, I should probably handle it at platform level to
avoid messing up generic ARMv7 suspend/resume routines.
Shawn
next prev parent reply other threads:[~2014-06-18 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 8:49 [PATCH] ARM: save/restore diagnostic register on ARMv7 suspend/resume Shawn Guo
2014-06-18 10:40 ` Will Deacon
2014-06-18 12:39 ` Shawn Guo [this message]
2014-06-18 13:07 ` Russell King - ARM Linux
2014-06-18 14:37 ` Nicolas Pitre
2014-06-18 15:04 ` Shawn Guo
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=20140618123906.GI8860@dragon \
--to=shawn.guo@freescale.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox