On Thu, 11 Jun 2009, Oliver Neukum wrote: > 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. What tree constraint? You mean that the PM core shouldn't allow devices to suspend unless all their children are suspended? Why doesn't it still apply? Remember, when Rafael and I say "suspend" here, we don't mean "go to a low-power state". We mean "the PM core calls the runtime_suspend method". No matter what actions the link hardware may decide to take on its own, the PM core will still want to observe the all-children-suspended restriction when calling runtime_suspend methods. > 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. Clearly it should be decided by the driver. Should there be a bit for it in the dev_pm_info structure? Alan Stern -- 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
