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:54:49 +0800 [thread overview]
Message-ID: <20140617145448.GH8860@dragon> (raw)
In-Reply-To: <20140617143415.GH13808@arm.com>
On Tue, Jun 17, 2014 at 03:34:15PM +0100, Will Deacon wrote:
> 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.
Thanks for the confirmation, Will.
Shawn
next prev parent reply other threads:[~2014-06-17 14:54 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 [this message]
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=20140617145448.GH8860@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;
as well as URLs for NNTP newsgroup(s).