sysfs-devices-power 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307
  1. What: /sys/devices/.../power/
  2. Date: January 2009
  3. Contact: Rafael J. Wysocki <[email protected]>
  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 <[email protected]>
  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 <[email protected]>
  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 <[email protected]>
  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 <[email protected]>
  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 capable to wake up
  72. the system from sleep states, this attribute is not present.
  73. If the device is not enabled to wake up the system from sleep
  74. states, this attribute is empty.
  75. What: /sys/devices/.../power/wakeup_active_count
  76. Date: September 2010
  77. Contact: Rafael J. Wysocki <[email protected]>
  78. Description:
  79. The /sys/devices/.../wakeup_active_count attribute contains the
  80. number of times the processing of wakeup events associated with
  81. the device was completed (at the kernel level). This attribute
  82. is read-only. If the device is not capable to wake up the
  83. system from sleep states, this attribute is not present. If
  84. the device is not enabled to wake up the system from sleep
  85. states, this attribute is empty.
  86. What: /sys/devices/.../power/wakeup_abort_count
  87. Date: February 2012
  88. Contact: Rafael J. Wysocki <[email protected]>
  89. Description:
  90. The /sys/devices/.../wakeup_abort_count attribute contains the
  91. number of times the processing of a wakeup event associated with
  92. the device might have aborted system transition into a sleep
  93. state in progress. This attribute is read-only. If the device
  94. is not capable to wake up the system from sleep states, this
  95. attribute is not present. If the device is not enabled to wake
  96. up the system from sleep states, this attribute is empty.
  97. What: /sys/devices/.../power/wakeup_expire_count
  98. Date: February 2012
  99. Contact: Rafael J. Wysocki <[email protected]>
  100. Description:
  101. The /sys/devices/.../wakeup_expire_count attribute contains the
  102. number of times a wakeup event associated with the device has
  103. been reported with a timeout that expired. This attribute is
  104. read-only. If the device is not capable to wake up the system
  105. from sleep states, this attribute is not present. If the
  106. device is not enabled to wake up the system from sleep states,
  107. this attribute is empty.
  108. What: /sys/devices/.../power/wakeup_active
  109. Date: September 2010
  110. Contact: Rafael J. Wysocki <[email protected]>
  111. Description:
  112. The /sys/devices/.../wakeup_active attribute contains either 1,
  113. or 0, depending on whether or not a wakeup event associated with
  114. the device is being processed (1). This attribute is read-only.
  115. If the device is not capable to wake up the system from sleep
  116. states, this attribute is not present. If the device is not
  117. enabled to wake up the system from sleep states, this attribute
  118. is empty.
  119. What: /sys/devices/.../power/wakeup_total_time_ms
  120. Date: September 2010
  121. Contact: Rafael J. Wysocki <[email protected]>
  122. Description:
  123. The /sys/devices/.../wakeup_total_time_ms attribute contains
  124. the total time of processing wakeup events associated with the
  125. device, in milliseconds. This attribute is read-only. If the
  126. device is not capable to wake up the system from sleep states,
  127. this attribute is not present. If the device is not enabled to
  128. wake up the system from sleep states, this attribute is empty.
  129. What: /sys/devices/.../power/wakeup_max_time_ms
  130. Date: September 2010
  131. Contact: Rafael J. Wysocki <[email protected]>
  132. Description:
  133. The /sys/devices/.../wakeup_max_time_ms attribute contains
  134. the maximum time of processing a single wakeup event associated
  135. with the device, in milliseconds. This attribute is read-only.
  136. If the device is not capable to wake up the system from sleep
  137. states, this attribute is not present. If the device is not
  138. enabled to wake up the system from sleep states, this attribute
  139. is empty.
  140. What: /sys/devices/.../power/wakeup_last_time_ms
  141. Date: September 2010
  142. Contact: Rafael J. Wysocki <[email protected]>
  143. Description:
  144. The /sys/devices/.../wakeup_last_time_ms attribute contains
  145. the value of the monotonic clock corresponding to the time of
  146. signaling the last wakeup event associated with the device, in
  147. milliseconds. This attribute is read-only. If the device is
  148. not enabled to wake up the system from sleep states, this
  149. attribute is not present. If the device is not enabled to wake
  150. up the system from sleep states, this attribute is empty.
  151. What: /sys/devices/.../power/wakeup_prevent_sleep_time_ms
  152. Date: February 2012
  153. Contact: Rafael J. Wysocki <[email protected]>
  154. Description:
  155. The /sys/devices/.../wakeup_prevent_sleep_time_ms attribute
  156. contains the total time the device has been preventing
  157. opportunistic transitions to sleep states from occurring.
  158. This attribute is read-only. If the device is not capable to
  159. wake up the system from sleep states, this attribute is not
  160. present. If the device is not enabled to wake up the system
  161. from sleep states, this attribute is empty.
  162. What: /sys/devices/.../power/autosuspend_delay_ms
  163. Date: September 2010
  164. Contact: Alan Stern <[email protected]>
  165. Description:
  166. The /sys/devices/.../power/autosuspend_delay_ms attribute
  167. contains the autosuspend delay value (in milliseconds). Some
  168. drivers do not want their device to suspend as soon as it
  169. becomes idle at run time; they want the device to remain
  170. inactive for a certain minimum period of time first. That
  171. period is called the autosuspend delay. Negative values will
  172. prevent the device from being suspended at run time (similar
  173. to writing "on" to the power/control attribute). Values >=
  174. 1000 will cause the autosuspend timer expiration to be rounded
  175. up to the nearest second.
  176. Not all drivers support this attribute. If it isn't supported,
  177. attempts to read or write it will yield I/O errors.
  178. What: /sys/devices/.../power/pm_qos_resume_latency_us
  179. Date: March 2012
  180. Contact: Rafael J. Wysocki <[email protected]>
  181. Description:
  182. The /sys/devices/.../power/pm_qos_resume_latency_us attribute
  183. contains the PM QoS resume latency limit for the given device,
  184. which is the maximum allowed time it can take to resume the
  185. device, after it has been suspended at run time, from a resume
  186. request to the moment the device will be ready to process I/O,
  187. in microseconds. If it is equal to 0, however, this means that
  188. the PM QoS resume latency may be arbitrary and the special value
  189. "n/a" means that user space cannot accept any resume latency at
  190. all for the given device.
  191. Not all drivers support this attribute. If it isn't supported,
  192. it is not present.
  193. This attribute has no effect on system-wide suspend/resume and
  194. hibernation.
  195. What: /sys/devices/.../power/pm_qos_latency_tolerance_us
  196. Date: January 2014
  197. Contact: Rafael J. Wysocki <[email protected]>
  198. Description:
  199. The /sys/devices/.../power/pm_qos_latency_tolerance_us attribute
  200. contains the PM QoS active state latency tolerance limit for the
  201. given device in microseconds. That is the maximum memory access
  202. latency the device can suffer without any visible adverse
  203. effects on user space functionality. If that value is the
  204. string "any", the latency does not matter to user space at all,
  205. but hardware should not be allowed to set the latency tolerance
  206. for the device automatically.
  207. Reading "auto" from this file means that the maximum memory
  208. access latency for the device may be determined automatically
  209. by the hardware as needed. Writing "auto" to it allows the
  210. hardware to be switched to this mode if there are no other
  211. latency tolerance requirements from the kernel side.
  212. This attribute is only present if the feature controlled by it
  213. is supported by the hardware.
  214. This attribute has no effect on runtime suspend and resume of
  215. devices and on system-wide suspend/resume and hibernation.
  216. What: /sys/devices/.../power/pm_qos_no_power_off
  217. Date: September 2012
  218. Contact: Rafael J. Wysocki <[email protected]>
  219. Description:
  220. The /sys/devices/.../power/pm_qos_no_power_off attribute
  221. is used for manipulating the PM QoS "no power off" flag. If
  222. set, this flag indicates to the kernel that power should not
  223. be removed entirely from the device.
  224. Not all drivers support this attribute. If it isn't supported,
  225. it is not present.
  226. This attribute has no effect on system-wide suspend/resume and
  227. hibernation.
  228. What: /sys/devices/.../power/runtime_status
  229. Date: April 2010
  230. Contact: Rafael J. Wysocki <[email protected]>
  231. Description:
  232. The /sys/devices/.../power/runtime_status attribute contains
  233. the current runtime PM status of the device, which may be
  234. "suspended", "suspending", "resuming", "active", "error" (fatal
  235. error), or "unsupported" (runtime PM is disabled).
  236. What: /sys/devices/.../power/runtime_active_time
  237. Date: Jul 2010
  238. Contact: Arjan van de Ven <[email protected]>
  239. Description:
  240. Reports the total time that the device has been active.
  241. Used for runtime PM statistics.
  242. What: /sys/devices/.../power/runtime_suspended_time
  243. Date: Jul 2010
  244. Contact: Arjan van de Ven <[email protected]>
  245. Description:
  246. Reports total time that the device has been suspended.
  247. Used for runtime PM statistics.
  248. What: /sys/devices/.../power/runtime_usage
  249. Date: Apr 2010
  250. Contact: Dominik Brodowski <[email protected]>
  251. Description:
  252. Reports the runtime PM usage count of a device.
  253. What: /sys/devices/.../power/runtime_enabled
  254. Date: Apr 2010
  255. Contact: Dominik Brodowski <[email protected]>
  256. Description:
  257. Is runtime PM enabled for this device?
  258. States are "enabled", "disabled", "forbidden" or a
  259. combination of the latter two.
  260. What: /sys/devices/.../power/runtime_active_kids
  261. Date: Apr 2010
  262. Contact: Dominik Brodowski <[email protected]>
  263. Description:
  264. Reports the runtime PM children usage count of a device, or
  265. 0 if the children will be ignored.