[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AANLkTi=VaayMuiU-RXnL40gf3_y0YWYvOWayDofdDmpL@mail.gmail.com>
Date: Mon, 13 Dec 2010 16:53:37 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: ykaoua@...lcomm.com
Cc: David Brown <davidb@...eaurora.org>,
Daniel Walker <dwalker@...eaurora.org>,
linux-arm-msm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Jeff Ohlstein <johlstei@...eaurora.org>,
Brian Swetland <swetland@...gle.com>,
Dima Zavin <dima@...roid.com>,
Arve Hjønnevåg <arve@...roid.com>,
Bryan Huntsman <bryanh@...eaurora.org>,
Russell King <linux@....linux.org.uk>
Subject: Re: [PATCH v3 4/5] msm: hotplug: support cpu hotplug on msm
On 13 December 2010 15:12, Catalin Marinas <catalin.marinas@....com> wrote:
> On 13 December 2010 01:20, <ykaoua@...lcomm.com> wrote:
>> --- /dev/null
>> +++ b/arch/arm/mach-msm/hotplug.c
> [...]
>> +static inline void platform_do_lowpower(unsigned int cpu)
>> +{
>> + /* Just enter wfe for now. */
>> + for (;;) {
>> + asm("wfe");
>> + if (pen_release == cpu) {
>> + /*
>> + * OK, proper wakeup, we're done
>> + */
>> + break;
>> + }
>> + smp_rmb();
>
> Do you need some barrier after wfe?
I checked with the hw people and it looks like we don't need a DSB
after an WFE (as you have in headsmp.S) since the hardware doesn't
speculate the loads beyond the WFE (lower power state). But in the
above case you may need some compiler barrier to avoid code
reordering.
--
Catalin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists