* Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> [110708 21:01]: > On Tue, Jun 28, 2011 at 01:47:47PM -0600, Paul Walmsley wrote: > > On Fri, 24 Jun 2011, Arve Hj?nnev?g wrote: > > > On Fri, Jun 24, 2011 at 12:53 PM, Paul Walmsley <paul@xxxxxxxxx> wrote: > > > > > "On the hardware that shipped we enter the same power state from idle > > > > and suspend, so the only power savings we get from suspend that we > > > > don't get in idle is from not respecting the scheduler and timers." > > > > This is no longer the case. Both the Nexus-S and Xoom enter lower > > > power states from suspend than idle. > > > Just out of curiosity, is that due to some kind of hardware limitation on > > those platforms, or is it because the software infrastructure for dynamic > > deep idle hasn't been fully implemented in that subarchitecture code? > > At least the Nexus S doesn't implmeent any of the deep idle > infrastructure. However, I'd expect that you can achieve some power > saving from entering system suspend as if *everything* is off then the > PMIC can be suspended which can enable additional power savings. Unless > I'm missing something that'd be hard to hit with cpuidle only stuff. You should be able to hit the same states from idle no problem. At that point the only things on are memory in retention and some wake-up timer. Even the timer could be off if you have hardware wake-up events, but then system timer won't work the noral way naturally. The only way power down everything in suspend to disk :) Most PMICs have some functionality always on so they can charge the battery when it's empty. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
