On Wed, Jun 02, 2010 at 11:12:39PM -0700, Brian Swetland wrote: > On Wed, Jun 2, 2010 at 11:04 PM, mark gross <640e9920@xxxxxxxxx> 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. > Oh. I thought everything went through hardware/libhardware_legacy/power/power.c who else is hitting /sys/power/* in the android user mode then? I'll have to go hunting for them I guess. --mgross -- 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
