On Mon, May 17, 2010 at 09:39:05PM +0300, Felipe Balbi wrote: > On Mon, May 17, 2010 at 11:26:59AM -0700, Brian Swetland wrote: > > For a large majority of apps, running in the background while the > > device is asleep (screen off) is not essential, they don't request the > > "keep device awake" permission, never hold a wakelock, etc. Those > > that do need to do this have the permission, may hold suspend > > blockers, and are accounted for. > but can anyone write an app that holds a suspend_blocker ?? If so, then > your goal is already broken, right ? I mean, if anyone can keep a > suspend_blocker held forever, you'll never ever sleep, right ? While > with runtime, if you keep the keypad open, only the keypad and the paths > directly related to it (probably the i2c controller and the power domain > where the i2c controller sits) will be kept alive, no ? The Android UI provides a list of which applications have been preventing suspend and how long for, the idea being that if something has been holding suspend blockers for ever you can at least look at the list and see what it was. -- 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
