[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100804214031.GD5864@sirena.org.uk>
Date: Wed, 4 Aug 2010 22:40:32 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Pavel Machek <pavel@....cz>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Matthew Garrett <mjg59@...f.ucam.org>,
Arjan van de Ven <arjan@...radead.org>,
Arve Hj?nnev?g <arve@...roid.com>,
linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
florian@...kler.org, rjw@...k.pl, stern@...land.harvard.edu,
swetland@...gle.com, peterz@...radead.org, tglx@...utronix.de,
alan@...rguk.ukuu.org.uk
Subject: Re: Attempted summary of suspend-blockers LKML thread
On Wed, Aug 04, 2010 at 11:15:13PM +0200, Pavel Machek wrote:
> > > In different message, Arve said they are actually using low-power idle
> > > to emulate suspend on Android.
> > Could you please point me at this message?
> AFAICT, this tells us that idle and suspend is the same hardware state
> on current Android hardware:
This is all massively system dependant. On some systems when the system
is in the same idle state in the lowest power idle mode as in suspend
however as a result of not doing the suspend (which causes Linux to
quiesce most of the hardware) many more things will be able to generate
wake events. On other systems you will achieve a lower power state by
using suspend for various reasons, some fixable and some not. I rather
suspect Arve was talking about the former case.
--
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