I'm trying to put together a 2.6.27 (from the 2.6.27 tag) kernel with power management, and what I'm seeing is a bit weird...
When I put it into "mem" state (i.e. save to DRAM and sleep the world, leaving DRAM alive), I see current consumption actually *increase*. Also, any interrupt (touch, serial, mmc insert/removal) automagicaly wakes it up. Any pointers on how to make sense of this? I would have thought that drivers have to specify which interrupts are capable of waking the core... -- Peter Barada <[email protected]> -- 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
