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 15:34:15 +0100 [thread overview]
Message-ID: <20140617143415.GH13808@arm.com> (raw)
In-Reply-To: <20140617130333.GE8860@dragon>
On Tue, Jun 17, 2014 at 02:03:35PM +0100, Shawn Guo wrote:
> On Tue, Jun 17, 2014 at 11:25:20AM +0100, Will Deacon wrote:
> > On Tue, Jun 17, 2014 at 11:23:44AM +0100, Russell King - ARM Linux wrote:
> > > On Tue, Jun 17, 2014 at 11:21:23AM +0100, Will Deacon wrote:
> > > > 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.
> > >
> > > Are you saying that it is write one to set, and writing zero is ignored?
> > > If that's true, we should simplify the work-around code to get rid of the
> > > read-modify-write.
> >
> > That's my understanding for the diagnostic register, but I've asked for
> > clarification internally.
>
> Hmm, I'm not sure that's the case. On imx6q, I can read out diagnostic
> register as 0x00200850 which matches the errata we enable.
The hardware guys got back to me, and I was mistaken (in fact, confused by
another register). So the diagnostic register on A9 *does* read back with
the value written to it. You still need to save/restore it across suspend,
but read-modify-write is the right thing to do everywhere else.
Will
next prev parent reply other threads:[~2014-06-17 14:34 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 [this message]
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=20140617143415.GH13808@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 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.