diff options
Diffstat (limited to 'Documentation/pm.txt')
-rw-r--r-- | Documentation/pm.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/pm.txt b/Documentation/pm.txt index 79c0f32a760e..da8589a0e07d 100644 --- a/Documentation/pm.txt +++ b/Documentation/pm.txt | |||
@@ -18,10 +18,10 @@ enabled by default). If a working ACPI implementation is found, the | |||
18 | ACPI driver will override and disable APM, otherwise the APM driver | 18 | ACPI driver will override and disable APM, otherwise the APM driver |
19 | will be used. | 19 | will be used. |
20 | 20 | ||
21 | No sorry, you can not have both ACPI and APM enabled and running at | 21 | No, sorry, you cannot have both ACPI and APM enabled and running at |
22 | once. Some people with broken ACPI or broken APM implementations | 22 | once. Some people with broken ACPI or broken APM implementations |
23 | would like to use both to get a full set of working features, but you | 23 | would like to use both to get a full set of working features, but you |
24 | simply can not mix and match the two. Only one power management | 24 | simply cannot mix and match the two. Only one power management |
25 | interface can be in control of the machine at once. Think about it.. | 25 | interface can be in control of the machine at once. Think about it.. |
26 | 26 | ||
27 | User-space Daemons | 27 | User-space Daemons |
@@ -106,7 +106,7 @@ void pm_unregister_all(pm_callback cback); | |||
106 | * | 106 | * |
107 | * Returns: 0 if the request is successful | 107 | * Returns: 0 if the request is successful |
108 | * EINVAL if the request is not supported | 108 | * EINVAL if the request is not supported |
109 | * EBUSY if the device is now busy and can not handle the request | 109 | * EBUSY if the device is now busy and cannot handle the request |
110 | * ENOMEM if the device was unable to handle the request due to memory | 110 | * ENOMEM if the device was unable to handle the request due to memory |
111 | * | 111 | * |
112 | * Details: The device request callback will be called before the | 112 | * Details: The device request callback will be called before the |