From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM diagnostic register across suspend/resume
Date: Tue, 17 Jun 2014 11:21:23 +0100 [thread overview]
Message-ID: <20140617102123.GA13808@arm.com> (raw)
In-Reply-To: <20140617101606.GE23430@n2100.arm.linux.org.uk>
On Tue, Jun 17, 2014 at 11:16:06AM +0100, Russell King - ARM Linux wrote:
> On Tue, Jun 17, 2014 at 10:57:29AM +0100, Will Deacon wrote:
> > On Tue, Jun 17, 2014 at 09:31:18AM +0100, Shawn Guo wrote:
> > > Hi Will, Catalin,
> > >
> > > The CP15 diagnostic register holds some bits for ARM errata workaround.
> > > Since core gets power gated across suspend/resume cycle, these bits will
> > > get lost along the way. Is it okay for errata workaround to continue
> > > working after suspend, or do we have to save/restore diagnostic register
> > > to keep workaround effective?
> >
> > I'm not sure that saving/restoring the diagnostic register on A9 actually
> > works at all (I seem to remember some bits always read as zero?).
>
> If that's true, then we have a problem. We always read-modify-write
> this register when enabling work-arounds. If it always reads as
> zero, then enabling a subsequent work-around will disable the
> previous work-around.
I think that actually works ok, because writing zeroes doesn't actually
do anything as far as I understand. The problem with suspend/resume is
that the suspend/resume cycle could well clear the internal state and
writing zeroes won't re-enable the workaround bits.
I'll double-check this with the hardware guys, since this register really
is undocumented.
Will
next prev parent reply other threads:[~2014-06-17 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 8:31 ARM diagnostic register across suspend/resume Shawn Guo
2014-06-17 9:57 ` Will Deacon
2014-06-17 10:16 ` Russell King - ARM Linux
2014-06-17 10:21 ` Will Deacon [this message]
2014-06-17 10:23 ` Russell King - ARM Linux
2014-06-17 10:25 ` Will Deacon
2014-06-17 13:03 ` Shawn Guo
2014-06-17 14:34 ` Will Deacon
2014-06-17 14:54 ` Shawn Guo
2014-06-17 13:08 ` Shawn Guo
2014-06-17 14:02 ` 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=20140617102123.GA13808@arm.com \
--to=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).