From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: smp_scu: enable SCU standby support
Date: Thu, 24 Jul 2014 16:49:46 +0800 [thread overview]
Message-ID: <20140724084945.GB8821@dragon> (raw)
In-Reply-To: <20140723164521.GF20966@arm.com>
On Wed, Jul 23, 2014 at 05:45:21PM +0100, Catalin Marinas wrote:
> On Wed, Jul 23, 2014 at 05:50:57AM +0100, Shawn Guo wrote:
> > On Tue, Jul 22, 2014 at 05:13:31PM +0100, Catalin Marinas wrote:
> > > And we don't know the behaviour of setting this bit on such A9 early
> > > revisions. So we can try to (1) find out if there are any in the field,
> > > (2) read the RTL to see if anything happens or (3) add a check in Linux
> > > for such revisions. I think (3) should be the case but you need to figure
> > > out which revisions these are.
> >
> > Can I ask the favor from you ARM folks on that, since I cannot figure
> > it out from any public information?
>
> Looking through some of the older A9 TRMs, it seems that this bit was
> added in r2p0. Whether it works as advertised on the relevant SoCs I
> can't tell.
Thanks for checking, Catalin.
Shawn
next prev parent reply other threads:[~2014-07-24 8:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 7:45 [PATCH 0/3] Enable SCU standby support at core level Shawn Guo
2014-07-21 7:45 ` [PATCH 1/3] ARM: smp_scu: use macro for SCU enable bit Shawn Guo
2014-07-21 7:45 ` [PATCH 2/3] ARM: smp_scu: enable SCU standby support Shawn Guo
2014-07-21 8:51 ` Will Deacon
2014-07-21 9:27 ` Shawn Guo
2014-07-21 9:44 ` Will Deacon
2014-07-22 1:56 ` Shawn Guo
2014-07-21 10:26 ` Catalin Marinas
2014-07-22 2:09 ` Shawn Guo
2014-07-22 16:13 ` Catalin Marinas
2014-07-23 4:50 ` Shawn Guo
2014-07-23 16:45 ` Catalin Marinas
2014-07-24 8:49 ` Shawn Guo [this message]
2014-07-21 7:45 ` [PATCH 3/3] ARM: imx: remove SCU standby enable code 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=20140724084945.GB8821@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 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.