Lines Matching refs:the
6 allowing the user space to check and modify some power
13 The /sys/devices/.../power/wakeup attribute allows the user
14 space to check if the device is enabled to wake up the system
15 from sleep states, such as the memory sleep state (suspend to
20 used to activate the system from a sleep state. Such devices
21 have one of the following two values for the sysfs power/wakeup
24 + "enabled\n" to issue the events;
27 In that cases the user space can change the setting represented
28 by the contents of this file by writing either "enabled", or
31 For the devices that are not capable of generating system wakeup
32 events this file is not present. In that case the device cannot
33 be enabled to wake up the system from sleep states.
39 The /sys/devices/.../power/control attribute allows the user
40 space to control the run-time power management of the device.
42 All devices have one of the following two values for the
45 + "auto\n" to allow the device to be power managed at run time;
46 + "on\n" to prevent the device from being power managed;
50 drivers. Changing this attribute to "on" prevents the driver
51 from power managing the device at run time. Doing that while
52 the device is suspended causes it to be woken up.
58 The /sys/devices/.../async attribute allows the user space to
59 enable or diasble the device's suspend and resume callbacks to
61 with the main suspend/resume thread) during system-wide power
64 All devices have one of the following two values for the
67 + "enabled\n" to permit the asynchronous suspend/resume;
73 It generally is unsafe to permit the asynchronous suspend/resume
74 of a device unless it is certain that all of the PM dependencies
75 of the device are known to the PM core. However, for some
77 device drivers and in that cases it should be safe to leave the
84 The /sys/devices/.../wakeup_count attribute contains the number
85 of signaled wakeup events associated with the device. This
86 attribute is read-only. If the device is not capable to wake up
87 the system from sleep states, this attribute is not present.
88 If the device is not enabled to wake up the system from sleep
95 The /sys/devices/.../wakeup_active_count attribute contains the
96 number of times the processing of wakeup events associated with
97 the device was completed (at the kernel level). This attribute
98 is read-only. If the device is not capable to wake up the
100 the device is not enabled to wake up the system from sleep
107 The /sys/devices/.../wakeup_abort_count attribute contains the
108 number of times the processing of a wakeup event associated with
109 the device might have aborted system transition into a sleep
110 state in progress. This attribute is read-only. If the device
111 is not capable to wake up the system from sleep states, this
112 attribute is not present. If the device is not enabled to wake
113 up the system from sleep states, this attribute is empty.
119 The /sys/devices/.../wakeup_expire_count attribute contains the
120 number of times a wakeup event associated with the device has
122 read-only. If the device is not capable to wake up the system
123 from sleep states, this attribute is not present. If the
124 device is not enabled to wake up the system from sleep states,
133 the device is being processed (1). This attribute is read-only.
134 If the device is not capable to wake up the system from sleep
135 states, this attribute is not present. If the device is not
136 enabled to wake up the system from sleep states, this attribute
144 the total time of processing wakeup events associated with the
145 device, in milliseconds. This attribute is read-only. If the
146 device is not capable to wake up the system from sleep states,
147 this attribute is not present. If the device is not enabled to
148 wake up the system from sleep states, this attribute is empty.
155 the maximum time of processing a single wakeup event associated
156 with the device, in milliseconds. This attribute is read-only.
157 If the device is not capable to wake up the system from sleep
158 states, this attribute is not present. If the device is not
159 enabled to wake up the system from sleep states, this attribute
167 the value of the monotonic clock corresponding to the time of
168 signaling the last wakeup event associated with the device, in
169 milliseconds. This attribute is read-only. If the device is
170 not enabled to wake up the system from sleep states, this
171 attribute is not present. If the device is not enabled to wake
172 up the system from sleep states, this attribute is empty.
179 contains the total time the device has been preventing
181 This attribute is read-only. If the device is not capable to
182 wake up the system from sleep states, this attribute is not
183 present. If the device is not enabled to wake up the system
191 contains the autosuspend delay value (in milliseconds). Some
193 becomes idle at run time; they want the device to remain
195 period is called the autosuspend delay. Negative values will
196 prevent the device from being suspended at run time (similar
197 to writing "on" to the power/control attribute). Values >=
198 1000 will cause the autosuspend timer expiration to be rounded
199 up to the nearest second.
209 contains the PM QoS resume latency limit for the given device,
210 which is the maximum allowed time it can take to resume the
212 request to the moment the device will be ready to process I/O,
214 the PM QoS resume latency may be arbitrary.
227 contains the PM QoS active state latency tolerance limit for the
228 given device in microseconds. That is the maximum memory access
229 latency the device can suffer without any visible adverse
230 effects on user space functionality. If that value is the
231 string "any", the latency does not matter to user space at all,
232 but hardware should not be allowed to set the latency tolerance
233 for the device automatically.
235 Reading "auto" from this file means that the maximum memory
236 access latency for the device may be determined automatically
237 by the hardware as needed. Writing "auto" to it allows the
239 latency tolerance requirements from the kernel side.
241 This attribute is only present if the feature controlled by it
242 is supported by the hardware.
252 is used for manipulating the PM QoS "no power off" flag. If
253 set, this flag indicates to the kernel that power should not
254 be removed entirely from the device.
267 is used for manipulating the PM QoS "remote wakeup required"
268 flag. If set, this flag indicates to the kernel that the