On Thu, Aug 13, 2009 at 10:47:01PM +0100, Matthew Garrett wrote: > Ugh. I'd really prefer us to assume that drivers are able to cope unless > proven otherwise. Userspace policy makes sense where we don't have any > idea whether something will work or not, but I'd really expect that most > PCI drivers will either cope (in which case they'll have enabling code) > or won't (in which case they won't). Why would we want userspace to > influence this? Though, thinking about it, you're right that setting this does override user policy. I think we need an additional flag to indicate that the device supports runtime wakeup and test that as well when doing device_may_wakeup(). > > This misses the point. The whole idea of runtime_idle is to tell you > > that the device is idle and might be ready to be suspended. If you're > > going to call pm_schedule_suspend anyway, there's no reason to invoke > > pm->runtime_idle. > > My understanding of the API was that pm_device_put() invokes > runtime_idle if the refcount hits 0. The bus layer has no idea of the > refcount, and calling suspend directly from the driver would defeat the > point of the system-wide recounting. >From the API docs: "The action performed by a bus type's ->runtime_idle() callback is totally dependent on the bus type in question, but the expected and recommended action is to check if the device can be suspended (i.e. if all of the conditions necessary for suspending the device are satisfied) and to queue up a suspend request for the device in that case." Though perhaps the device level runtime_idle shouldn't be void - that way the bus can ask the driver whether its suspend conditions have been satisfied? Right now there doesn't seem to be any way for the bus to ask that. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
