diff options
Diffstat (limited to 'Documentation/ABI/testing/sysfs-power')
-rw-r--r-- | Documentation/ABI/testing/sysfs-power | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/Documentation/ABI/testing/sysfs-power b/Documentation/ABI/testing/sysfs-power index dcff4d0623ad..2875f1f74a07 100644 --- a/Documentation/ABI/testing/sysfs-power +++ b/Documentation/ABI/testing/sysfs-power | |||
@@ -101,3 +101,31 @@ Description: | |||
101 | 101 | ||
102 | CAUTION: Using it will cause your machine's real-time (CMOS) | 102 | CAUTION: Using it will cause your machine's real-time (CMOS) |
103 | clock to be set to a random invalid time after a resume. | 103 | clock to be set to a random invalid time after a resume. |
104 | |||
105 | What: /sys/power/pm_async | ||
106 | Date: January 2009 | ||
107 | Contact: Rafael J. Wysocki <rjw@sisk.pl> | ||
108 | Description: | ||
109 | The /sys/power/pm_async file controls the switch allowing the | ||
110 | user space to enable or disable asynchronous suspend and resume | ||
111 | of devices. If enabled, this feature will cause some device | ||
112 | drivers' suspend and resume callbacks to be executed in parallel | ||
113 | with each other and with the main suspend thread. It is enabled | ||
114 | if this file contains "1", which is the default. It may be | ||
115 | disabled by writing "0" to this file, in which case all devices | ||
116 | will be suspended and resumed synchronously. | ||
117 | |||
118 | What: /sys/power/wakeup_count | ||
119 | Date: July 2010 | ||
120 | Contact: Rafael J. Wysocki <rjw@sisk.pl> | ||
121 | Description: | ||
122 | The /sys/power/wakeup_count file allows user space to put the | ||
123 | system into a sleep state while taking into account the | ||
124 | concurrent arrival of wakeup events. Reading from it returns | ||
125 | the current number of registered wakeup events and it blocks if | ||
126 | some wakeup events are being processed at the time the file is | ||
127 | read from. Writing to it will only succeed if the current | ||
128 | number of wakeup events is equal to the written value and, if | ||
129 | successful, will make the kernel abort a subsequent transition | ||
130 | to a sleep state if any wakeup events are reported after the | ||
131 | write has returned. | ||