On Sunday 05 July 2009, Alan Stern wrote: > On Sat, 4 Jul 2009, Rafael J. Wysocki wrote: > > > > As for whether or not we should actually call cancel_work... Which is > > > more expensive: Calling cancel_work when no work is pending, or letting > > > the work item run when it doesn't have anything to do? Probably the > > > latter. > > > > Agreed, but that doesn't affect functionality. We can get the desired > > functionality without the cancel_work() patch and then optimize things along > > with that patch. This way it'll be easier to demontrate the benefit of it. > > Good idea. > > > That almost entirely depends on the bus type. For PCI and probably PNP as well > > there's a notion of ACPI low power states and there are AML methods to put the > > devices into these states. Unfortunately, the ACPI low power state to put the > > device into depends on the target sleep state of the system, so these devices > > will probably have to be put into D0 before system suspend anyway. > > > > I think that the bus type can handle this as long as it knows the state the > > device is in before system suspend. So, the only thing the core should do is > > to block the execution of run-time PM framework functions during system > > sleep and resume. The state it leaves the device in shouldn't matter. > > > > So, I think we can simply freeze the workqueue, set the 'disabled' bit for each > > device and wait for all run-time PM operations on it in progress to complete. > > > > In the 'disabled' state the bus type or driver can modify the run-time PM > > status to whatever they like anyway. Perhaps we can provide a helper to > > change 'request type' to RPM_REQ_NONE. > > The only modification that really makes sense is like you said, going > back to full power in preparation for the platform suspend operation. > Therefore perhaps we should allow pm_runtime_resume to work even when > rpm_disabled is set. And if we're going to cancel pending suspend and > idle requests, then rpm_request would normally be RPM_REQ_NONE anyway. After we've disabled run-time PM with pm_runtime_disable(), the bus type and driver can do whatever they like with the device, we don't care. However, they need to make sure that the state of the device will match its run-time PM status when its run-time PM is enabled again. > Which leaves only the question of what to do when a resume request is > pending... I think the pm_runtime_disable() can carry out a synchronous wake-up if it sees a pending resume request. That would make sense in general, IMO, becuase having a resume request pending usually means there's I/O to process and it's better to allow the device to process that I/O before disabling the run-time PM of it. To put it differently, if there's a resume request pending, the run-time PM of the device should be disabled while in the 'active' state rather than while in the 'suspended' state. Now, if we do that, the problem of run-time resume requests pending while entering a system sleep state can be solved. Namely, we can make pm_runtime_disable() return a result that will be -EBUSY if a pending resume request is found by it and 0 otherwise. Then, that result can be used by dpm_prepare() to decide whether to continue suspend or to terminate it if the device is a wake-up one. > > So, I guess we have the majority of things clarified and perhaps its time to > > write a patch for further discussion. :-) > > Go ahead! In fact I've already done that, but I need to have a final look at it to check if there are no obvious mistakes in there. Best, Rafael _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
