sysfs-devices-power 9.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238
  1. What: /sys/devices/.../power/
  2. Date: January 2009
  3. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  4. Description:
  5. The /sys/devices/.../power directory contains attributes
  6. allowing the user space to check and modify some power
  7. management related properties of given device.
  8. What: /sys/devices/.../power/wakeup
  9. Date: January 2009
  10. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  11. Description:
  12. The /sys/devices/.../power/wakeup attribute allows the user
  13. space to check if the device is enabled to wake up the system
  14. from sleep states, such as the memory sleep state (suspend to
  15. RAM) and hibernation (suspend to disk), and to enable or disable
  16. it to do that as desired.
  17. Some devices support "wakeup" events, which are hardware signals
  18. used to activate the system from a sleep state. Such devices
  19. have one of the following two values for the sysfs power/wakeup
  20. file:
  21. + "enabled\n" to issue the events;
  22. + "disabled\n" not to do so;
  23. In that cases the user space can change the setting represented
  24. by the contents of this file by writing either "enabled", or
  25. "disabled" to it.
  26. For the devices that are not capable of generating system wakeup
  27. events this file is not present. In that case the device cannot
  28. be enabled to wake up the system from sleep states.
  29. What: /sys/devices/.../power/control
  30. Date: January 2009
  31. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  32. Description:
  33. The /sys/devices/.../power/control attribute allows the user
  34. space to control the run-time power management of the device.
  35. All devices have one of the following two values for the
  36. power/control file:
  37. + "auto\n" to allow the device to be power managed at run time;
  38. + "on\n" to prevent the device from being power managed;
  39. The default for all devices is "auto", which means that they may
  40. be subject to automatic power management, depending on their
  41. drivers. Changing this attribute to "on" prevents the driver
  42. from power managing the device at run time. Doing that while
  43. the device is suspended causes it to be woken up.
  44. What: /sys/devices/.../power/async
  45. Date: January 2009
  46. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  47. Description:
  48. The /sys/devices/.../async attribute allows the user space to
  49. enable or diasble the device's suspend and resume callbacks to
  50. be executed asynchronously (ie. in separate threads, in parallel
  51. with the main suspend/resume thread) during system-wide power
  52. transitions (eg. suspend to RAM, hibernation).
  53. All devices have one of the following two values for the
  54. power/async file:
  55. + "enabled\n" to permit the asynchronous suspend/resume;
  56. + "disabled\n" to forbid it;
  57. The value of this attribute may be changed by writing either
  58. "enabled", or "disabled" to it.
  59. It generally is unsafe to permit the asynchronous suspend/resume
  60. of a device unless it is certain that all of the PM dependencies
  61. of the device are known to the PM core. However, for some
  62. devices this attribute is set to "enabled" by bus type code or
  63. device drivers and in that cases it should be safe to leave the
  64. default value.
  65. What: /sys/devices/.../power/wakeup_count
  66. Date: September 2010
  67. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  68. Description:
  69. The /sys/devices/.../wakeup_count attribute contains the number
  70. of signaled wakeup events associated with the device. This
  71. attribute is read-only. If the device is not enabled to wake up
  72. the system from sleep states, this attribute is not present.
  73. What: /sys/devices/.../power/wakeup_active_count
  74. Date: September 2010
  75. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  76. Description:
  77. The /sys/devices/.../wakeup_active_count attribute contains the
  78. number of times the processing of wakeup events associated with
  79. the device was completed (at the kernel level). This attribute
  80. is read-only. If the device is not enabled to wake up the
  81. system from sleep states, this attribute is not present.
  82. What: /sys/devices/.../power/wakeup_abort_count
  83. Date: February 2012
  84. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  85. Description:
  86. The /sys/devices/.../wakeup_abort_count attribute contains the
  87. number of times the processing of a wakeup event associated with
  88. the device might have aborted system transition into a sleep
  89. state in progress. This attribute is read-only. If the device
  90. is not enabled to wake up the system from sleep states, this
  91. attribute is not present.
  92. What: /sys/devices/.../power/wakeup_expire_count
  93. Date: February 2012
  94. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  95. Description:
  96. The /sys/devices/.../wakeup_expire_count attribute contains the
  97. number of times a wakeup event associated with the device has
  98. been reported with a timeout that expired. This attribute is
  99. read-only. If the device is not enabled to wake up the system
  100. from sleep states, this attribute is not present.
  101. What: /sys/devices/.../power/wakeup_active
  102. Date: September 2010
  103. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  104. Description:
  105. The /sys/devices/.../wakeup_active attribute contains either 1,
  106. or 0, depending on whether or not a wakeup event associated with
  107. the device is being processed (1). This attribute is read-only.
  108. If the device is not enabled to wake up the system from sleep
  109. states, this attribute is not present.
  110. What: /sys/devices/.../power/wakeup_total_time_ms
  111. Date: September 2010
  112. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  113. Description:
  114. The /sys/devices/.../wakeup_total_time_ms attribute contains
  115. the total time of processing wakeup events associated with the
  116. device, in milliseconds. This attribute is read-only. If the
  117. device is not enabled to wake up the system from sleep states,
  118. this attribute is not present.
  119. What: /sys/devices/.../power/wakeup_max_time_ms
  120. Date: September 2010
  121. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  122. Description:
  123. The /sys/devices/.../wakeup_max_time_ms attribute contains
  124. the maximum time of processing a single wakeup event associated
  125. with the device, in milliseconds. This attribute is read-only.
  126. If the device is not enabled to wake up the system from sleep
  127. states, this attribute is not present.
  128. What: /sys/devices/.../power/wakeup_last_time_ms
  129. Date: September 2010
  130. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  131. Description:
  132. The /sys/devices/.../wakeup_last_time_ms attribute contains
  133. the value of the monotonic clock corresponding to the time of
  134. signaling the last wakeup event associated with the device, in
  135. milliseconds. This attribute is read-only. If the device is
  136. not enabled to wake up the system from sleep states, this
  137. attribute is not present.
  138. What: /sys/devices/.../power/wakeup_prevent_sleep_time_ms
  139. Date: February 2012
  140. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  141. Description:
  142. The /sys/devices/.../wakeup_prevent_sleep_time_ms attribute
  143. contains the total time the device has been preventing
  144. opportunistic transitions to sleep states from occuring.
  145. This attribute is read-only. If the device is not enabled to
  146. wake up the system from sleep states, this attribute is not
  147. present.
  148. What: /sys/devices/.../power/autosuspend_delay_ms
  149. Date: September 2010
  150. Contact: Alan Stern <stern@rowland.harvard.edu>
  151. Description:
  152. The /sys/devices/.../power/autosuspend_delay_ms attribute
  153. contains the autosuspend delay value (in milliseconds). Some
  154. drivers do not want their device to suspend as soon as it
  155. becomes idle at run time; they want the device to remain
  156. inactive for a certain minimum period of time first. That
  157. period is called the autosuspend delay. Negative values will
  158. prevent the device from being suspended at run time (similar
  159. to writing "on" to the power/control attribute). Values >=
  160. 1000 will cause the autosuspend timer expiration to be rounded
  161. up to the nearest second.
  162. Not all drivers support this attribute. If it isn't supported,
  163. attempts to read or write it will yield I/O errors.
  164. What: /sys/devices/.../power/pm_qos_latency_us
  165. Date: March 2012
  166. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  167. Description:
  168. The /sys/devices/.../power/pm_qos_resume_latency_us attribute
  169. contains the PM QoS resume latency limit for the given device,
  170. which is the maximum allowed time it can take to resume the
  171. device, after it has been suspended at run time, from a resume
  172. request to the moment the device will be ready to process I/O,
  173. in microseconds. If it is equal to 0, however, this means that
  174. the PM QoS resume latency may be arbitrary.
  175. Not all drivers support this attribute. If it isn't supported,
  176. it is not present.
  177. This attribute has no effect on system-wide suspend/resume and
  178. hibernation.
  179. What: /sys/devices/.../power/pm_qos_no_power_off
  180. Date: September 2012
  181. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  182. Description:
  183. The /sys/devices/.../power/pm_qos_no_power_off attribute
  184. is used for manipulating the PM QoS "no power off" flag. If
  185. set, this flag indicates to the kernel that power should not
  186. be removed entirely from the device.
  187. Not all drivers support this attribute. If it isn't supported,
  188. it is not present.
  189. This attribute has no effect on system-wide suspend/resume and
  190. hibernation.
  191. What: /sys/devices/.../power/pm_qos_remote_wakeup
  192. Date: September 2012
  193. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  194. Description:
  195. The /sys/devices/.../power/pm_qos_remote_wakeup attribute
  196. is used for manipulating the PM QoS "remote wakeup required"
  197. flag. If set, this flag indicates to the kernel that the
  198. device is a source of user events that have to be signaled from
  199. its low-power states.
  200. Not all drivers support this attribute. If it isn't supported,
  201. it is not present.
  202. This attribute has no effect on system-wide suspend/resume and
  203. hibernation.