Lines Matching refs:runtime_suspend

47 	int (*runtime_suspend)(struct device *dev);
53 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
79 the PM core that it is safe to run the ->runtime_suspend(), ->runtime_resume()
88 include executing the device driver's own ->runtime_suspend() callback (from the
89 PM core's point of view it is not necessary to implement a ->runtime_suspend()
115 device, then ->runtime_suspend() should return -EBUSY.  On the other hand, if
166     ->runtime_suspend() in parallel with ->runtime_resume() or with another
167     instance of ->runtime_suspend() for the same device) with the exception that
168     ->runtime_suspend() or ->runtime_resume() can be executed in parallel with
172 (2) ->runtime_idle() and ->runtime_suspend() can only be executed for 'active'
174     ->runtime_suspend() for the devices the runtime PM status of which is
177 (3) ->runtime_idle() and ->runtime_suspend() can only be executed for a device
189   * If ->runtime_suspend() is about to be executed or there's a pending request
192   * A request to execute or to schedule the execution of ->runtime_suspend()
257     - set if ->runtime_resume() is about to be run while ->runtime_suspend() is
282     - indicates that the ->runtime_suspend() and ->runtime_resume() callbacks
368       ->runtime_suspend() is already scheduled and not yet expired, the new
745     - invoke the ->runtime_suspend() callback provided by the driver of this
807 provide its own callbacks for ->runtime_idle(), ->runtime_suspend(),
826 need of runtime PM callbacks; if the callbacks did exist, ->runtime_suspend()
837 ->runtime_idle(), ->runtime_suspend(), or ->runtime_resume() callbacks.
895 autosuspend delay time has expired.  If the ->runtime_suspend() callback
899 autosuspend.  The ->runtime_suspend() callback can't do this rescheduling
905 synchronize ->runtime_suspend() callbacks with the arrival of I/O requests.
969 pm_runtime_autosuspend_expiration() from within the ->runtime_suspend()