On Fri, May 28, 2010 at 6:29 AM, Pavel Machek <pavel@xxxxxx> wrote: > Hi! > >> > > Why would you need to constantly try to suspend in that case? >> > >> > Because otherwise you're awake for longer than you need to be. >> >> If your system is idle and your hardware supports off-while-idle, >> then that really does not matter. There's not much of a difference >> in power savings, we're already talking over 10 days on batteries >> with just off-while-idle on omaps. > > Makes me wish g1 was omap based... it looks like you have superior hw. G1 will happily do 10 days idle (radio on) under typical network conditions (roughly 4-5mA draw at the battery average in paging mode) if you have data disabled and there's no reason for it to wake up, process events, chat on the data network etc. It'll go 25-30 days in "airplane mode" (radio off) provided there are not excessive wakeups. If you happen to be running a perfect userspace where every thread in every process is blocked on something, it'll hit the exact same power state out of idle. If you have a less optimal userspace or random third party nonoptimal apps, this becomes much harder, of course. Which is why we do the wakelock thing. OMAP does have a lot of nice auto-clock-down features compared to some other SoCs, sometimes simplifying other parts of power management. Brian _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
