Lines Matching refs:runtime
9 Support for runtime power management (runtime PM) of I/O devices is provided
14 used for queuing all work items related to runtime PM, because this allows
19 * A number of runtime PM fields in the 'power' member of 'struct device' (which
21 be used for synchronizing runtime PM operations with one another.
23 * Three device runtime PM callbacks in 'struct dev_pm_ops' (defined in
26 * A set of helper functions defined in drivers/base/power/runtime.c that can be
27 used for carrying out runtime PM operations in such a way that the
31 The runtime PM callbacks present in 'struct dev_pm_ops', the device runtime PM
33 runtime PM are described below.
37 There are three device runtime PM callbacks defined in 'struct dev_pm_ops':
92 RAM until the appropriate resume callback is executed for it. The runtime
96 * If the suspend callback returns -EBUSY or -EAGAIN, the device's runtime PM
125 I/O operations as needed. The runtime PM status of the device is then
149 0, then the PM core will attempt to carry out a runtime suspend of the device,
158 that the following constraints are met with respect to runtime PM callbacks for
170 ->runtime_suspend() for the devices the runtime PM status of which is
179 PM core will only execute ->runtime_resume() for the devices the runtime
201 The following device runtime PM fields are present in 'struct dev_pm_info', as
233 equal to zero); the initial value of it is 1 (i.e. runtime PM is
257 - set if the device is capable of generating runtime wake-up events
260 - the runtime PM status of the device; this field's initial value is
271 - indicates that the device does not use the runtime PM callbacks (see
300 The following runtime PM helper functions are defined in
301 drivers/base/power/runtime.c and include/linux/pm_runtime.h:
304 - initialize the device runtime PM fields in 'struct dev_pm_info'
307 - make sure that the runtime PM of the device will be disabled after
318 success, 1 if the device's runtime PM status was already 'suspended', or
331 success, 1 if the device's runtime PM status was already 'active' or
352 runtime status was already 'suspended', or error code if the request
360 success, 1 if the device's runtime PM status was already 'active', or
399 to zero, the runtime PM helper functions can execute subsystem-level
404 field was previously zero, this prevents subsystem-level runtime PM
406 pending runtime PM operations on the device are either completed or
413 (synchronously) in that case, cancel any other pending runtime PM requests
414 regarding it and wait for all runtime PM operations on it in progress to
423 - clear the device's 'power.runtime_error' flag, set the device's runtime
431 - clear the device's 'power.runtime_error' flag, set the device's runtime
438 - return true if the device's runtime PM status is 'active' or its
442 - return true if the device's runtime PM status is 'suspended' and its
446 - return true if the device's runtime PM status is 'suspended'
459 - set the power.no_callbacks flag for the device and remove the runtime
464 - set the power.irq_safe flag for the device, causing the runtime-PM
469 the runtime-PM callbacks to be invoked with interrupts off
482 milliseconds); if 'delay' is negative then runtime suspends are
526 Initially, the runtime PM is disabled for all devices, which means that the
527 majority of the runtime PM helper functions described in Section 4 will return
530 In addition to that, the initial runtime PM status of all devices is
533 runtime PM status must be changed to 'active', with the help of
536 However, if the device has a parent and the parent's runtime PM is enabled,
541 runtime PM is still disabled (i.e. pm_runtime_enable() hasn't been called for
544 should be called for it too as soon as reasonably possible or its runtime PM
548 If the default initial runtime PM status of the device (i.e. 'suspended')
552 should be used. Of course, for this purpose the device's runtime PM has to be
564 time. A driver that makes use of the runtime autosuspend feature, may want to
567 Moreover, the driver core prevents runtime PM callbacks from racing with the bus
570 runtime PM functionality. It does so by calling pm_runtime_get_sync() before
579 drivers to make their ->remove() callbacks avoid races with runtime PM directly,
587 runtime power management of the device until the user space turns it on.
588 Namely, during the initialization the driver can make sure that the runtime PM
602 The device may have different wake-up settings for runtime PM and system sleep.
603 For example, remote wake-up may be enabled for runtime suspend but disallowed
609 or other settings for runtime suspend and system sleep.
628 likely it would need a runtime resume in the near future anyway.
631 brought back to full power during resume, then its runtime PM status will have
639 The PM core always increments the runtime usage counter before calling the
641 Hence disabling runtime PM temporarily like this will not cause any runtime
661 that the device appears to be runtime-suspended and its state is fine, so it
662 may be left in runtime suspend provided that all of its descendants are also
663 left in runtime suspend. If that happens, the PM core will not execute any
671 the runtime PM and system suspend/resume (and hibernation) callbacks by carrying
713 if successful, change the device's runtime PM status to 'active'
750 if successful, change the device's runtime PM status to 'active'
763 poweroff and runtime suspend callback, and similarly for system resume, thaw,
764 restore, and runtime resume, can achieve this with the help of the
774 need of runtime PM callbacks; if the callbacks did exist, ->runtime_suspend()
782 prevent the non-debugging runtime PM sysfs attributes from being created.
790 or driver about runtime power changes. Instead, the driver for the device's
801 at runtime until they have been inactive for some minimum period. Even when
807 the appropriate PM routines); rather it means that runtime suspends will