public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM diagnostic register across suspend/resume
Date: Tue, 17 Jun 2014 22:02:46 +0800	[thread overview]
Message-ID: <20140617140245.GB7299@dragon> (raw)
In-Reply-To: <20140617130827.GF8860@dragon>

On Tue, Jun 17, 2014 at 09:08:28PM +0800, Shawn Guo 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?).
> > 
> > Anyway, I'd expect the state could be lost, so you'd need to reprogram
> > the diagnostic register rather than save/restore its value.
> 
> Yes, we observed that diagnostic state gets lost after suspend.  But
> per my testing I can see the effectiveness of errata workaround
> preserves.  Is this expected somehow or something wrong in my testing?

It is something wrong in my testing.  The effectiveness of errata
workaround goes off together with diagnostic register state.

Shawn

      reply	other threads:[~2014-06-17 14:02 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
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 [this message]

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=20140617140245.GB7299@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