Lines Matching refs:to
6 allowing the user space to check and modify some power
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
16 RAM) and hibernation (suspend to disk), and to enable or disable
17 it to do that as desired.
20 used to activate the system from a sleep state. Such devices
24 + "enabled\n" to issue the events;
25 + "disabled\n" not to do so;
29 "disabled" to it.
33 be enabled to wake up the system from sleep states.
40 space to control the run-time power management of the device.
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;
49 be subject to automatic power management, depending on their
50 drivers. Changing this attribute to "on" prevents the driver
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
62 transitions (eg. suspend to RAM, hibernation).
67 + "enabled\n" to permit the asynchronous suspend/resume;
68 + "disabled\n" to forbid it;
71 "enabled", or "disabled" to it.
73 It generally is unsafe to permit the asynchronous suspend/resume
75 of the device are known to the PM core. However, for some
76 devices this attribute is set to "enabled" by bus type code or
77 device drivers and in that cases it should be safe to leave the
86 attribute is read-only. If the device is not capable to wake up
88 If the device is not enabled to wake up the system from sleep
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
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
122 read-only. If the device is not capable to wake up the system
124 device is not enabled to wake up the system from sleep states,
134 If the device is not capable to wake up the system from sleep
136 enabled to wake up the system from sleep states, this attribute
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
157 If the device is not capable to wake up the system from sleep
159 enabled to wake up the system from sleep states, this attribute
167 the value of the monotonic clock corresponding to the time of
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
180 opportunistic transitions to sleep states from occurring.
181 This attribute is read-only. If the device is not capable to
183 present. If the device is not enabled to wake up the system
192 drivers do not want their device to suspend as soon as it
193 becomes idle at run time; they want the device to remain
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.
202 attempts to read or write it will yield I/O errors.
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,
213 in microseconds. If it is equal to 0, however, this means that
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
237 by the hardware as needed. Writing "auto" to it allows the
238 hardware to be switched to this mode if there are no other
253 set, this flag indicates to the kernel that power should not
268 flag. If set, this flag indicates to the kernel that the
269 device is a source of user events that have to be signaled from