> Rather than continue going around in circles, let's agree that what the > Android people want is a new version of forced suspend -- not a I don't think this is true. I think that is the root of the problem. I don't disagree with the user experience they are trying to create or the fact something is needed to make it possible (if it turns out we can't already do it). Forced suspend is sticking stuff in running state into suspend Power management models (such as Thomas ARM box) which we know work are 'when nothing is running' into suspend. So for me the real question on that side of this specific case is 'how do you make sure those tasks are idle when you need them to be' QoS ? Spanking them from user space ? Drivers enforcing policy elements by blocking tasks ? Alan -- 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
