Lines Matching full:its
58 example, a parent device cannot be suspended unless all of its child
147 The :c:member:`power.can_wakeup` flag just records whether the device (and its
152 its system wakeup mechanism and for notifying the PM core of system wakeup
207 runtime power-managed by its driver. Writing "on" calls
216 system-wide transition to a sleep state even though its :c:member:`runtime_auto`
237 and then turn its hardware as "off" as possible during suspend_noirq. The
239 before reactivating its class I/O queues.
255 its parent; and can't be removed or suspended after that parent.
331 method must not update its state in case it is necessary to resume it
351 PM, then its prepare callback must never return a positive value. This
362 of its ancestors. The second flag, when set, informs the middle layer
365 into account and it may only return a positive value from its own
403 generated by some other device after its own device had been set to low
420 low-power state. Instead, the PM core will unwind its actions by resuming all
434 method should bring the device and its driver into a state in which the
448 3. The ``->resume`` methods should bring the device back to its operating
462 whole system suspend and resume (its ``->suspend``, ``->suspend_late``,
544 discussed earlier. The main difference is that its methods can assume
549 described above. Its methods should undo the actions of the preceding
553 earlier. Its methods should bring the device back to an operating
683 its frame buffer might even be updated by a DSP or other non-Linux CPU while
714 from the object pointed to by it will be executed instead of its subsystem's
759 state temporarily, for example so that its system wakeup capability can be
767 device's driver or its subsystem (for example, a bus type or a PM domain).
828 In addition, a device is not allowed to remain in runtime suspend if any of its
836 clear :c:member:`power.may_skip_resume` in its ``->suspend``, ``->suspend_late``
850 during the preceding system-wide suspend transition and its
851 ``DPM_FLAG_SMART_SUSPEND`` is set, its runtime PM status will be set to
859 callbacks are skipped, its system-wide "noirq" and "early" resume callbacks, if
862 driver must be prepared to cope with the invocation of its system-wide resume
863 callbacks back-to-back with its ``->runtime_suspend`` one (without the
867 ``->suspend_late`` callback pointer points to the same function as its
868 ``->runtime_suspend`` one and its ``->resume_early`` callback pointer points to
872 Likewise, if ``DPM_FLAG_MAY_SKIP_RESUME`` is set for a device, its driver's
873 system-wide "noirq" and "early" resume callbacks may be skipped while its "late"
876 needs to be able to cope with the invocation of its ``->runtime_resume``
877 callback back-to-back with its "late" and "noirq" suspend ones. [For instance,