diff options
-rw-r--r-- | Documentation/power/devices.txt | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/Documentation/power/devices.txt b/Documentation/power/devices.txt index 4342acbeee1..ed322888413 100644 --- a/Documentation/power/devices.txt +++ b/Documentation/power/devices.txt | |||
@@ -250,7 +250,7 @@ for every device before the next phase begins. Not all busses or classes | |||
250 | support all these callbacks and not all drivers use all the callbacks. The | 250 | support all these callbacks and not all drivers use all the callbacks. The |
251 | various phases always run after tasks have been frozen and before they are | 251 | various phases always run after tasks have been frozen and before they are |
252 | unfrozen. Furthermore, the *_noirq phases run at a time when IRQ handlers have | 252 | unfrozen. Furthermore, the *_noirq phases run at a time when IRQ handlers have |
253 | been disabled (except for those marked with the IRQ_WAKEUP flag). | 253 | been disabled (except for those marked with the IRQF_NO_SUSPEND flag). |
254 | 254 | ||
255 | All phases use PM domain, bus, type, or class callbacks (that is, methods | 255 | All phases use PM domain, bus, type, or class callbacks (that is, methods |
256 | defined in dev->pm_domain->ops, dev->bus->pm, dev->type->pm, or dev->class->pm). | 256 | defined in dev->pm_domain->ops, dev->bus->pm, dev->type->pm, or dev->class->pm). |
@@ -295,9 +295,8 @@ When the system goes into the standby or memory sleep state, the phases are: | |||
295 | 295 | ||
296 | After the prepare callback method returns, no new children may be | 296 | After the prepare callback method returns, no new children may be |
297 | registered below the device. The method may also prepare the device or | 297 | registered below the device. The method may also prepare the device or |
298 | driver in some way for the upcoming system power transition (for | 298 | driver in some way for the upcoming system power transition, but it |
299 | example, by allocating additional memory required for this purpose), but | 299 | should not put the device into a low-power state. |
300 | it should not put the device into a low-power state. | ||
301 | 300 | ||
302 | 2. The suspend methods should quiesce the device to stop it from performing | 301 | 2. The suspend methods should quiesce the device to stop it from performing |
303 | I/O. They also may save the device registers and put it into the | 302 | I/O. They also may save the device registers and put it into the |