^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) What: /sys/devices/.../power/
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) Date: January 2009
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5) The /sys/devices/.../power directory contains attributes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) allowing the user space to check and modify some power
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) management related properties of given device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) What: /sys/devices/.../power/wakeup
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) Date: January 2009
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) The /sys/devices/.../power/wakeup attribute allows the user
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) space to check if the device is enabled to wake up the system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) from sleep states, such as the memory sleep state (suspend to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) RAM) and hibernation (suspend to disk), and to enable or disable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) it to do that as desired.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) Some devices support "wakeup" events, which are hardware signals
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) used to activate the system from a sleep state. Such devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) have one of the following two values for the sysfs power/wakeup
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) file:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) + "enabled\n" to issue the events;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) + "disabled\n" not to do so;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) In that cases the user space can change the setting represented
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) by the contents of this file by writing either "enabled", or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) "disabled" to it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) For the devices that are not capable of generating system wakeup
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) events this file is not present. In that case the device cannot
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) be enabled to wake up the system from sleep states.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) What: /sys/devices/.../power/control
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) Date: January 2009
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) The /sys/devices/.../power/control attribute allows the user
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) space to control the run-time power management of the device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) All devices have one of the following two values for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) power/control file:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) + "auto\n" to allow the device to be power managed at run time;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) + "on\n" to prevent the device from being power managed;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) The default for all devices is "auto", which means that they may
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) be subject to automatic power management, depending on their
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) drivers. Changing this attribute to "on" prevents the driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) from power managing the device at run time. Doing that while
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52) the device is suspended causes it to be woken up.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) What: /sys/devices/.../power/async
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) Date: January 2009
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) The /sys/devices/.../async attribute allows the user space to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) enable or diasble the device's suspend and resume callbacks to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) be executed asynchronously (ie. in separate threads, in parallel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) with the main suspend/resume thread) during system-wide power
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) transitions (eg. suspend to RAM, hibernation).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) All devices have one of the following two values for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) power/async file:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) + "enabled\n" to permit the asynchronous suspend/resume;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) + "disabled\n" to forbid it;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70) The value of this attribute may be changed by writing either
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) "enabled", or "disabled" to it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) It generally is unsafe to permit the asynchronous suspend/resume
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74) of a device unless it is certain that all of the PM dependencies
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) of the device are known to the PM core. However, for some
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) devices this attribute is set to "enabled" by bus type code or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77) device drivers and in that cases it should be safe to leave the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) default value.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80) What: /sys/devices/.../power/wakeup_count
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) Date: September 2010
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) The /sys/devices/.../wakeup_count attribute contains the number
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) of signaled wakeup events associated with the device. This
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) attribute is read-only. If the device is not capable to wake up
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87) the system from sleep states, this attribute is not present.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) If the device is not enabled to wake up the system from sleep
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89) states, this attribute is empty.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91) What: /sys/devices/.../power/wakeup_active_count
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92) Date: September 2010
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95) The /sys/devices/.../wakeup_active_count attribute contains the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96) number of times the processing of wakeup events associated with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97) the device was completed (at the kernel level). This attribute
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) is read-only. If the device is not capable to wake up the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99) system from sleep states, this attribute is not present. If
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) the device is not enabled to wake up the system from sleep
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) states, this attribute is empty.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) What: /sys/devices/.../power/wakeup_abort_count
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) Date: February 2012
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) The /sys/devices/.../wakeup_abort_count attribute contains the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) number of times the processing of a wakeup event associated with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) the device might have aborted system transition into a sleep
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) state in progress. This attribute is read-only. If the device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) is not capable to wake up the system from sleep states, this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) attribute is not present. If the device is not enabled to wake
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) up the system from sleep states, this attribute is empty.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) What: /sys/devices/.../power/wakeup_expire_count
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) Date: February 2012
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) The /sys/devices/.../wakeup_expire_count attribute contains the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) number of times a wakeup event associated with the device has
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) been reported with a timeout that expired. This attribute is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) read-only. If the device is not capable to wake up the system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) from sleep states, this attribute is not present. If the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) device is not enabled to wake up the system from sleep states,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) this attribute is empty.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) What: /sys/devices/.../power/wakeup_active
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) Date: September 2010
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) The /sys/devices/.../wakeup_active attribute contains either 1,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) or 0, depending on whether or not a wakeup event associated with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) the device is being processed (1). This attribute is read-only.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) If the device is not capable to wake up the system from sleep
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) states, this attribute is not present. If the device is not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) enabled to wake up the system from sleep states, this attribute
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) is empty.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) What: /sys/devices/.../power/wakeup_total_time_ms
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) Date: September 2010
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) The /sys/devices/.../wakeup_total_time_ms attribute contains
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) the total time of processing wakeup events associated with the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) device, in milliseconds. This attribute is read-only. If the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) device is not capable to wake up the system from sleep states,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) this attribute is not present. If the device is not enabled to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) wake up the system from sleep states, this attribute is empty.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) What: /sys/devices/.../power/wakeup_max_time_ms
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) Date: September 2010
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) The /sys/devices/.../wakeup_max_time_ms attribute contains
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) the maximum time of processing a single wakeup event associated
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) with the device, in milliseconds. This attribute is read-only.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) If the device is not capable to wake up the system from sleep
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) states, this attribute is not present. If the device is not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) enabled to wake up the system from sleep states, this attribute
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) is empty.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) What: /sys/devices/.../power/wakeup_last_time_ms
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) Date: September 2010
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) The /sys/devices/.../wakeup_last_time_ms attribute contains
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) the value of the monotonic clock corresponding to the time of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) signaling the last wakeup event associated with the device, in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) milliseconds. This attribute is read-only. If the device is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) not enabled to wake up the system from sleep states, this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) attribute is not present. If the device is not enabled to wake
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) up the system from sleep states, this attribute is empty.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) What: /sys/devices/.../power/wakeup_prevent_sleep_time_ms
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175) Date: February 2012
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) The /sys/devices/.../wakeup_prevent_sleep_time_ms attribute
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) contains the total time the device has been preventing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) opportunistic transitions to sleep states from occurring.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) This attribute is read-only. If the device is not capable to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) wake up the system from sleep states, this attribute is not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) present. If the device is not enabled to wake up the system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) from sleep states, this attribute is empty.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) What: /sys/devices/.../power/autosuspend_delay_ms
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) Date: September 2010
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) Contact: Alan Stern <stern@rowland.harvard.edu>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) The /sys/devices/.../power/autosuspend_delay_ms attribute
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) contains the autosuspend delay value (in milliseconds). Some
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) drivers do not want their device to suspend as soon as it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) becomes idle at run time; they want the device to remain
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) inactive for a certain minimum period of time first. That
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) period is called the autosuspend delay. Negative values will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) prevent the device from being suspended at run time (similar
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) to writing "on" to the power/control attribute). Values >=
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) 1000 will cause the autosuspend timer expiration to be rounded
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) up to the nearest second.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) Not all drivers support this attribute. If it isn't supported,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202) attempts to read or write it will yield I/O errors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) What: /sys/devices/.../power/pm_qos_resume_latency_us
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) Date: March 2012
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) The /sys/devices/.../power/pm_qos_resume_latency_us attribute
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) contains the PM QoS resume latency limit for the given device,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) which is the maximum allowed time it can take to resume the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) device, after it has been suspended at run time, from a resume
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) request to the moment the device will be ready to process I/O,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) in microseconds. If it is equal to 0, however, this means that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) the PM QoS resume latency may be arbitrary and the special value
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) "n/a" means that user space cannot accept any resume latency at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) all for the given device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) Not all drivers support this attribute. If it isn't supported,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) it is not present.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) This attribute has no effect on system-wide suspend/resume and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) hibernation.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224) What: /sys/devices/.../power/pm_qos_latency_tolerance_us
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) Date: January 2014
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228) The /sys/devices/.../power/pm_qos_latency_tolerance_us attribute
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) contains the PM QoS active state latency tolerance limit for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) given device in microseconds. That is the maximum memory access
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231) latency the device can suffer without any visible adverse
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232) effects on user space functionality. If that value is the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) string "any", the latency does not matter to user space at all,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234) but hardware should not be allowed to set the latency tolerance
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235) for the device automatically.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) Reading "auto" from this file means that the maximum memory
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) access latency for the device may be determined automatically
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) by the hardware as needed. Writing "auto" to it allows the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) hardware to be switched to this mode if there are no other
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241) latency tolerance requirements from the kernel side.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243) This attribute is only present if the feature controlled by it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244) is supported by the hardware.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246) This attribute has no effect on runtime suspend and resume of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247) devices and on system-wide suspend/resume and hibernation.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) What: /sys/devices/.../power/pm_qos_no_power_off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) Date: September 2012
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253) The /sys/devices/.../power/pm_qos_no_power_off attribute
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254) is used for manipulating the PM QoS "no power off" flag. If
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255) set, this flag indicates to the kernel that power should not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256) be removed entirely from the device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258) Not all drivers support this attribute. If it isn't supported,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259) it is not present.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261) This attribute has no effect on system-wide suspend/resume and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262) hibernation.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) What: /sys/devices/.../power/runtime_status
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265) Date: April 2010
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 266) Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 267) Description:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 268) The /sys/devices/.../power/runtime_status attribute contains
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 269) the current runtime PM status of the device, which may be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 270) "suspended", "suspending", "resuming", "active", "error" (fatal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 271) error), or "unsupported" (runtime PM is disabled).