From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: CPUv6K (ARM1176) and wfi()
Date: Tue, 29 Mar 2011 11:58:46 +0100 [thread overview]
Message-ID: <20110329105846.GD2738@pulham.picochip.com> (raw)
In-Reply-To: <006d01cbedf0$c60d1070$52273150$@deacon@arm.com>
On Tue, Mar 29, 2011 at 10:07:47AM +0100, Will Deacon wrote:
> > On Mon, Mar 28, 2011 at 1:25 PM, Jamie Iles <jamie@jamieiles.com> wrote:
> > > Hi Catalin, Will,
> > >
> > > I'm respinning some PM patches for my platform (ARM1176JZ-S) and looking
> > > at arch/arm/include/asm/system.h, for CPU_32v6K wfi() uses the "wfi"
> > > instruction, but when I use this on my system the instruction returns
> > > immediately. ?Replacing this with:
> > >
> > > ? ? ? ?asm volatile("mcr ? p15, 0, %0, c7, c0, 4\n" :: "r"(0));
> > >
> > > makes everything work properly. ?The ARM1176 TRM doesn't mention the wfi
> > > instruction afaict but does say to use the cp15 instruction in section
> > > 10.2.2 (Standby mode). ?It doesn't look to me that the SEV or WFE
> > > instructions are implemented on ARM1176 so I'm guessing that these are
> > > only in mpcore?
> >
> > I think WFI/SEV/WFE are encoded as NOP-synonyms, so they may do
> > nothing on non-multicore platforms; so I think the MCR is the correct
> > mechanism to use for 1176... unless Will or Catalin have better ideas.
>
> Would using the mcr get in the way of a combined v6/v7 kernel image?
> I notice that the behaviour on A9 is the exact opposite (wfi works, mcr
> is a NOP).
Wouldnet it also be a problem for smp-on-up for a v6K only kernel? It
doesn't look like arm11 mpcore supports the cp15 access...
Jamie
next prev parent reply other threads:[~2011-03-29 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 12:25 CPUv6K (ARM1176) and wfi() Jamie Iles
2011-03-28 14:32 ` Dave Martin
2011-03-29 9:07 ` Will Deacon
2011-03-29 10:58 ` Jamie Iles [this message]
2011-03-29 11:26 ` Will Deacon
2011-03-29 11:30 ` Jamie Iles
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=20110329105846.GD2738@pulham.picochip.com \
--to=jamie@jamieiles.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.