sysfs-devices-power 6.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167
  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 contains "\n". In that cases the user space
  28. cannot modify the contents of this file and the device cannot be
  29. enabled to wake up the system.
  30. What: /sys/devices/.../power/control
  31. Date: January 2009
  32. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  33. Description:
  34. The /sys/devices/.../power/control attribute allows the user
  35. space to control the run-time power management of the device.
  36. All devices have one of the following two values for the
  37. power/control file:
  38. + "auto\n" to allow the device to be power managed at run time;
  39. + "on\n" to prevent the device from being power managed;
  40. The default for all devices is "auto", which means that they may
  41. be subject to automatic power management, depending on their
  42. drivers. Changing this attribute to "on" prevents the driver
  43. from power managing the device at run time. Doing that while
  44. the device is suspended causes it to be woken up.
  45. What: /sys/devices/.../power/async
  46. Date: January 2009
  47. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  48. Description:
  49. The /sys/devices/.../async attribute allows the user space to
  50. enable or diasble the device's suspend and resume callbacks to
  51. be executed asynchronously (ie. in separate threads, in parallel
  52. with the main suspend/resume thread) during system-wide power
  53. transitions (eg. suspend to RAM, hibernation).
  54. All devices have one of the following two values for the
  55. power/async file:
  56. + "enabled\n" to permit the asynchronous suspend/resume;
  57. + "disabled\n" to forbid it;
  58. The value of this attribute may be changed by writing either
  59. "enabled", or "disabled" to it.
  60. It generally is unsafe to permit the asynchronous suspend/resume
  61. of a device unless it is certain that all of the PM dependencies
  62. of the device are known to the PM core. However, for some
  63. devices this attribute is set to "enabled" by bus type code or
  64. device drivers and in that cases it should be safe to leave the
  65. default value.
  66. What: /sys/devices/.../power/wakeup_count
  67. Date: September 2010
  68. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  69. Description:
  70. The /sys/devices/.../wakeup_count attribute contains the number
  71. of signaled wakeup events associated with the device. This
  72. attribute is read-only. If the device is not enabled to wake up
  73. the system from sleep states, this attribute is empty.
  74. What: /sys/devices/.../power/wakeup_active_count
  75. Date: September 2010
  76. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  77. Description:
  78. The /sys/devices/.../wakeup_active_count attribute contains the
  79. number of times the processing of wakeup events associated with
  80. the device was completed (at the kernel level). This attribute
  81. is read-only. If the device is not enabled to wake up the
  82. system from sleep states, this attribute is empty.
  83. What: /sys/devices/.../power/wakeup_hit_count
  84. Date: September 2010
  85. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  86. Description:
  87. The /sys/devices/.../wakeup_hit_count attribute contains the
  88. number of times the processing of a wakeup event associated with
  89. the device might prevent the system from entering a sleep state.
  90. This attribute is read-only. If the device is not enabled to
  91. wake up the system from sleep states, this attribute is empty.
  92. What: /sys/devices/.../power/wakeup_active
  93. Date: September 2010
  94. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  95. Description:
  96. The /sys/devices/.../wakeup_active attribute contains either 1,
  97. or 0, depending on whether or not a wakeup event associated with
  98. the device is being processed (1). This attribute is read-only.
  99. If the device is not enabled to wake up the system from sleep
  100. states, this attribute is empty.
  101. What: /sys/devices/.../power/wakeup_total_time_ms
  102. Date: September 2010
  103. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  104. Description:
  105. The /sys/devices/.../wakeup_total_time_ms attribute contains
  106. the total time of processing wakeup events associated with the
  107. device, in milliseconds. This attribute is read-only. If the
  108. device is not enabled to wake up the system from sleep states,
  109. this attribute is empty.
  110. What: /sys/devices/.../power/wakeup_max_time_ms
  111. Date: September 2010
  112. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  113. Description:
  114. The /sys/devices/.../wakeup_max_time_ms attribute contains
  115. the maximum time of processing a single wakeup event associated
  116. with the device, in milliseconds. This attribute is read-only.
  117. If the device is not enabled to wake up the system from sleep
  118. states, this attribute is empty.
  119. What: /sys/devices/.../power/wakeup_last_time_ms
  120. Date: September 2010
  121. Contact: Rafael J. Wysocki <rjw@sisk.pl>
  122. Description:
  123. The /sys/devices/.../wakeup_last_time_ms attribute contains
  124. the value of the monotonic clock corresponding to the time of
  125. signaling the last wakeup event associated with the device, in
  126. milliseconds. This attribute is read-only. If the device is
  127. not enabled to wake up the system from sleep states, this
  128. attribute is empty.
  129. What: /sys/devices/.../power/autosuspend_delay_ms
  130. Date: September 2010
  131. Contact: Alan Stern <stern@rowland.harvard.edu>
  132. Description:
  133. The /sys/devices/.../power/autosuspend_delay_ms attribute
  134. contains the autosuspend delay value (in milliseconds). Some
  135. drivers do not want their device to suspend as soon as it
  136. becomes idle at run time; they want the device to remain
  137. inactive for a certain minimum period of time first. That
  138. period is called the autosuspend delay. Negative values will
  139. prevent the device from being suspended at run time (similar
  140. to writing "on" to the power/control attribute). Values >=
  141. 1000 will cause the autosuspend timer expiration to be rounded
  142. up to the nearest second.
  143. Not all drivers support this attribute. If it isn't supported,
  144. attempts to read or write it will yield I/O errors.