From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mach-moxart: platform port for MOXA ART SoC
Date: Thu, 16 May 2013 15:35:03 +0200 [thread overview]
Message-ID: <201305161535.03742.arnd@arndb.de> (raw)
In-Reply-To: <20130516085711.GP18614@n2100.arm.linux.org.uk>
On Thursday 16 May 2013, Russell King - ARM Linux wrote:
> Well, if its a CPU core thing, then it's even easier - the proc-*.S
> file can handle it just fine (because that's where the WFI code is.)
> Just delete the contents of the processor specific idle function, IOW:
>
> /*
> * cpu_fa526_do_idle()
> */
> .align 4
> ENTRY(cpu_fa526_do_idle)
> mcr p15, 0, r0, c7, c0, 4 @ Wait for interrupt
> mov pc, lr
>
> remove the WFI from there.
Yes, that was what I meant.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: "Russell King - ARM Linux" <linux@arm.linux.org.uk>
Cc: Jonas Jensen <jonas.jensen@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Daniel Mack <zonque@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: mach-moxart: platform port for MOXA ART SoC
Date: Thu, 16 May 2013 15:35:03 +0200 [thread overview]
Message-ID: <201305161535.03742.arnd@arndb.de> (raw)
In-Reply-To: <20130516085711.GP18614@n2100.arm.linux.org.uk>
On Thursday 16 May 2013, Russell King - ARM Linux wrote:
> Well, if its a CPU core thing, then it's even easier - the proc-*.S
> file can handle it just fine (because that's where the WFI code is.)
> Just delete the contents of the processor specific idle function, IOW:
>
> /*
> * cpu_fa526_do_idle()
> */
> .align 4
> ENTRY(cpu_fa526_do_idle)
> mcr p15, 0, r0, c7, c0, 4 @ Wait for interrupt
> mov pc, lr
>
> remove the WFI from there.
Yes, that was what I meant.
Arnd
next prev parent reply other threads:[~2013-05-16 13:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 15:51 ARM: mach-moxart: platform port for MOXA ART SoC Jonas Jensen
[not found] ` <CACmBeS01vs=fHOXu1Lnq8GX8YAbF6aBKmqopKPVt78mPYm=_9w@mail.gmail.com>
2013-03-13 15:37 ` [PATCH] " Jonas Jensen
2013-03-13 15:37 ` Jonas Jensen
2013-03-13 18:34 ` Daniel Mack
2013-03-13 18:34 ` Daniel Mack
2013-03-15 11:25 ` Arnd Bergmann
2013-03-15 11:25 ` Arnd Bergmann
2013-03-17 15:32 ` Jonas Jensen
2013-03-17 15:32 ` Jonas Jensen
2013-03-18 15:03 ` Arnd Bergmann
2013-03-18 15:03 ` Arnd Bergmann
2013-05-15 11:20 ` Jonas Jensen
2013-05-15 11:20 ` Jonas Jensen
2013-05-15 13:16 ` Arnd Bergmann
2013-05-15 13:16 ` Arnd Bergmann
2013-05-15 13:32 ` Russell King - ARM Linux
2013-05-15 13:32 ` Russell King - ARM Linux
2013-05-15 22:54 ` Arnd Bergmann
2013-05-15 22:54 ` Arnd Bergmann
2013-05-16 8:57 ` Russell King - ARM Linux
2013-05-16 8:57 ` Russell King - ARM Linux
2013-05-16 13:35 ` Arnd Bergmann [this message]
2013-05-16 13:35 ` Arnd Bergmann
2013-05-16 13:50 ` Jonas Jensen
2013-05-16 13:50 ` Jonas Jensen
2013-05-16 13:37 ` Jonas Jensen
2013-05-16 13:37 ` Jonas Jensen
2013-05-16 14:52 ` Arnd Bergmann
2013-05-16 14:52 ` Arnd Bergmann
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=201305161535.03742.arnd@arndb.de \
--to=arnd@arndb.de \
--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.