From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/8] ARM: vexpress: use generic cpu idle function for wfi
Date: Tue, 11 Jun 2013 11:07:25 +0100 [thread overview]
Message-ID: <1370945245.3116.10.camel@hornet> (raw)
In-Reply-To: <51B6B691.1040305@linaro.org>
On Tue, 2013-06-11 at 06:33 +0100, Sanjay Singh Rawat wrote:
> >> use cpu_do_idle for entering the wfi mode.
> >>
> >> Signed-off-by: Sanjay Singh Rawat <sanjay.rawat@linaro.org>
> >> ---
> >> arch/arm/mach-vexpress/hotplug.c | 3 ++-
> >> 1 file changed, 2 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/arch/arm/mach-vexpress/hotplug.c b/arch/arm/mach-vexpress/hotplug.c
> >> index f0ce6b8..b3dffc2 100644
> >> --- a/arch/arm/mach-vexpress/hotplug.c
> >> +++ b/arch/arm/mach-vexpress/hotplug.c
> >> @@ -60,7 +60,8 @@ static inline void platform_do_lowpower(unsigned int cpu, int *spurious)
> >> * code will have already disabled interrupts
> >> */
> >> for (;;) {
> >> - wfi();
> >> + /* enter WFI mode */
> >> + cpu_do_idle();
> >>
> >> if (pen_release == cpu_logical_map(cpu)) {
> >> /*
> >
> > I probably don't get the whole picture, but may I ask what is the
> > rationale behind this change? As in: why cpu_do_idle() is better?
>
> commit: 8553cb67d2318db327071018fc81084cbabccc46 explains that
Oh, I've noticed the dsb there, I'm just asking why is it necessary in
the cpu_die() case? The core is going down anyway, it left the coherency
domain and we could cut the power now (if only it was possible). All
cache maintenance (which undoubtedly included dsb) has been long done.
Now, don't get me wrong - I'm not saying it's wrong to do the dsb. I
simply would like to know if and why is required (I'm admitting my
ignorance here ;-) But if you simply grep-ed for "wfi()" in the whole
kernel and automatically replaced them with "cpu_do_idle()", it doesn't
make sense.
Regards
Pawel
next prev parent reply other threads:[~2013-06-11 10:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 14:32 [PATCH 0/8] ARM: use cpu_do_idle for entering wfi mode Sanjay Singh Rawat
2013-05-27 14:32 ` [PATCH 1/8] ARM: EXYNOS: use generic cpu idle function for wfi Sanjay Singh Rawat
2013-06-04 15:25 ` Sanjay Singh Rawat
2013-05-27 14:32 ` [PATCH 2/8] ARM: RealView: " Sanjay Singh Rawat
2013-06-04 15:20 ` Sanjay Singh Rawat
2013-05-27 14:32 ` [PATCH 3/8] ARM: SPEAr: " Sanjay Singh Rawat
2013-05-28 9:55 ` Viresh Kumar
2013-05-27 14:32 ` [PATCH 4/8] ARM: vexpress: " Sanjay Singh Rawat
2013-06-04 15:23 ` Sanjay Singh Rawat
2013-06-07 9:17 ` Linus Walleij
2013-06-07 15:11 ` Pawel Moll
2013-06-11 5:33 ` Sanjay Singh Rawat
2013-06-11 10:07 ` Pawel Moll [this message]
2013-06-11 15:30 ` Nicolas Pitre
2013-06-12 5:34 ` Sanjay Singh Rawat
2013-05-27 14:32 ` [PATCH 5/8] ARM: zynq: " Sanjay Singh Rawat
2013-05-29 5:39 ` Michal Simek
2013-05-27 14:32 ` [PATCH 6/8] ARM: ux500: " Sanjay Singh Rawat
2013-05-30 7:26 ` Srinidhi Kasagar
2013-05-27 14:32 ` [PATCH 7/8] ARM: msm: " Sanjay Singh Rawat
2013-05-28 18:50 ` David Brown
2013-05-30 16:42 ` David Brown
2013-05-27 14:32 ` [PATCH 8/8] ARM: PRIMA2: " Sanjay Singh Rawat
2013-06-04 15:28 ` Sanjay Singh Rawat
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=1370945245.3116.10.camel@hornet \
--to=pawel.moll@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 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).