On Wed, Jun 2, 2010 at 11:04 PM, mark gross <[email protected]> wrote: >> >> There are many wakeup events possible in a typical system -- >> keypresses or other input events, network traffic, telephony events, >> media events (fill audio buffer, fill video decoder buffer, etc), and >> I think requiring that all wakeup event processing bottleneck through >> a single userspace process is non-optimal here. > > Um doesn't the android framework bottleneck the user mode lock > processing through the powermanager and any wake up event processing > eventually has to grab a lock through this bottleneck anyway?
For "high level" framework/application level wakelocks, yes, but lower level components beneath the java api layer use the kernel interface directly. Brian -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
