Lines Matching refs:methods
42 by implementing various role-specific suspend and resume methods to
69 various role-specific suspend and resume methods, so that the hardware
103 methods included in it will be explained in what follows. For now, it should be
104 sufficient to remember that the last three methods are specific to runtime power
111 sleep power management methods in a limited way. Therefore it is not described
119 The core methods to suspend and resume devices reside in
126 bus types) don't provide all power management methods.
128 Bus drivers implement these methods as appropriate for the hardware and the
279 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
304 driver-specific methods stored in ``dev->driver->pm``, but they don't have to do
369 2. The ``->suspend`` methods should quiesce the device to stop it from
375 ``->suspend`` methods provided by subsystems (bus types and PM domains
377 to the devices before their drivers' ``->suspend`` methods are called.
382 suspend in their ``->suspend`` methods). In fact, the PM core prevents
395 the callback method is running. The ``->suspend_noirq`` methods should
430 1. The ``->resume_noirq`` callback methods should perform any actions
444 2. The ``->resume_early`` methods should prepare devices for the execution
445 of the resume methods. This generally involves undoing the actions of
448 3. The ``->resume`` methods should bring the device back to its operating
486 suspend methods were called, for example by complete reinitialization.
525 2. The ``->freeze`` methods should quiesce the device so that it doesn't
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