Lines Matching refs:runtime_resume
48 int (*runtime_resume)(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()
123 include executing the device driver's own ->runtime_resume() callback (from the
124 PM core's point of view it is not necessary to implement a ->runtime_resume()
168 ->runtime_suspend() in parallel with ->runtime_resume() or with another
170 ->runtime_suspend() or ->runtime_resume() can be executed in parallel with
184 (4) ->runtime_resume() can only be executed for 'suspended' devices (i.e. the
185 PM core will only execute ->runtime_resume() for the devices the runtime
198 * If ->runtime_resume() is about to be executed or there's a pending request
201 * A request to execute ->runtime_resume() will cancel any pending or
259 - set if ->runtime_resume() is about to be run while ->runtime_suspend() is
280 - indicates that the ->runtime_suspend() and ->runtime_resume() callbacks
737 - invoke the ->runtime_resume() callback provided by the driver of this
796 ->runtime_resume(), ->suspend(), ->suspend_noirq(), ->resume(),
815 and ->runtime_resume() would always return 0 without doing anything else and
825 ->runtime_idle(), ->runtime_suspend(), or ->runtime_resume() callbacks.