Am Donnerstag, 11. Juni 2009 20:36:30 schrieb Alan Stern: > > Or abstractly any power saving state that does autoresume in hardware. > > In these cases you know that you can enter a powersaving state that > > will add X latency. > > > > In terms of user space API we'll probably add a way for user space > > to specify how much latency may be added for power management's sake. > > If busses are stacked the "latency budget" has to be handled at core > > level. If furthermore states that allow IO but with additional latency > > are ignored, the budget will be calculated wrongly. > > Okay, fine. What does this have to do with Rafael's work? Why does > setting the status to RPM_SUSPENDED even when a device is not in a > low-power state preclude handling buses that automatically change their > power state? For these cases the tree constraint does not apply. I think there are devices who can be suspended while children are active and devices which can not be. This is an attribute of the device and should be evaluated by the core. Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
