Lines Matching refs:callback
62 callback, the PM core will invoke the corresponding driver callback stored in
65 The PM core always checks which callback to use in the order given above, so the
75 interrupts disabled. This implies that the callback routines in question must
80 The subsystem-level suspend callback, if present, is _entirely_ _responsible_
82 include executing the device driver's own ->runtime_suspend() callback (from the
84 callback in a device driver as long as the subsystem-level suspend callback
87 * Once the subsystem-level suspend callback (or the driver suspend callback,
92 RAM until the appropriate resume callback is executed for it. The runtime
93 PM status of a device after successful execution of the suspend callback is
96 * If the suspend callback returns -EBUSY or -EAGAIN, the device's runtime PM
100 * If the suspend callback returns an error code different from -EBUSY and
111 low-power state during the execution of the suspend callback, it is expected
115 The subsystem-level resume callback, if present, is _entirely_ _responsible_ for
117 include executing the device driver's own ->runtime_resume() callback (from the
119 callback in a device driver as long as the subsystem-level resume callback knows
122 * Once the subsystem-level resume callback (or the driver resume callback, if
128 * If the resume callback returns an error code, the PM core regards this as a
134 The idle callback (a subsystem-level one, if present, or the driver one) is
142 idle callback with the device as its argument.
144 The action performed by the idle callback is totally dependent on the subsystem
148 device in that case. If there is no idle callback, or if the callback returns
153 this circumstance). To prevent this (for example, if the callback routine has
240 callback
311 - execute the subsystem-level idle callback for the device; returns an
313 already being executed; if there is no callback or the callback returns 0
317 - execute the subsystem-level suspend callback for the device; returns 0 on
330 - execute the subsystem-level resume callback for the device; returns 0 on
338 - submit a request to execute the subsystem-level idle callback for the
343 - schedule the execution of the subsystem-level suspend callback for the
348 - schedule the execution of the subsystem-level suspend callback for the
358 - submit a request to execute the subsystem-level resume callback for the
408 necessary to execute the subsystem-level resume callback for the device
416 necessary to execute the subsystem-level resume callback for the device to
550 ->probe() callback will likely need to wake it up using one of the PM core's
563 request to execute the subsystem-level idle callback for the device at that
568 notifier callback in __device_release_driver(), which is necessary, because the
605 the subsystem-level system suspend callback is responsible for changing the
640 ->suspend() callback and decrements it after calling the ->resume() callback.
643 following the return of the ->resume() callback, the ->runtime_idle() callback
660 callback returns a positive number for a device, that indicates to the PM core
665 complete callback, which is then entirely responsible for handling the device
675 right before executing the subsystem-level .prepare() callback for it and
677 subsystem-level .suspend() callback for it. In addition to that the PM core
679 device right before executing the subsystem-level .suspend_late() callback
684 callback and right after executing the subsystem-level .complete() callback
694 - invoke the ->runtime_suspend() callback provided by the driver of this
698 - invoke the ->runtime_resume() callback provided by the driver of this
703 callback provided by its driver and return its result, or return 0 if not
708 callback provided by the device's driver and return its result, or return
712 - invoke the ->resume() callback provided by the driver of this device and,
716 - invoke the ->resume_noirq() callback provided by the driver of this device
720 callback provided by its driver and return its result, or return 0 if not
725 callback provided by the device's driver and return its result, or return
730 callback provided by its driver and return its result, or return 0 if not
735 callback provided by the device's driver and return its result, or return
740 callback provided by its driver and return its result, or return 0 if not
745 callback provided by the device's driver and return its result, or return
749 - invoke the ->restore() callback provided by the driver of this device and,
753 - invoke the ->restore_noirq() callback provided by the device's driver
763 poweroff and runtime suspend callback, and similarly for system resume, thaw,
835 autosuspend delay time has expired. If the ->runtime_suspend() callback
837 in the future (as it normally would be if the callback invoked
839 autosuspend. The ->runtime_suspend() callback can't do this rescheduling
841 suspending (i.e., while the callback is running).
904 the foo_runtime_suspend() callback may race with foo_read_or_write().
912 callback while holding its private lock. If the function returns a nonzero
913 value then the delay has not yet expired and the callback should return