sysfs-bus-acpi 3.4 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798
  1. What: /sys/bus/acpi/devices/.../path
  2. Date: December 2006
  3. Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
  4. Description:
  5. This attribute indicates the full path of ACPI namespace
  6. object associated with the device object. For example,
  7. \_SB_.PCI0.
  8. This file is not present for device objects representing
  9. fixed ACPI hardware features (like power and sleep
  10. buttons).
  11. What: /sys/bus/acpi/devices/.../modalias
  12. Date: July 2007
  13. Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
  14. Description:
  15. This attribute indicates the PNP IDs of the device object.
  16. That is acpi:HHHHHHHH:[CCCCCCC:]. Where each HHHHHHHH or
  17. CCCCCCCC contains device object's PNPID (_HID or _CID).
  18. What: /sys/bus/acpi/devices/.../hid
  19. Date: April 2005
  20. Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
  21. Description:
  22. This attribute indicates the hardware ID (_HID) of the
  23. device object. For example, PNP0103.
  24. This file is present for device objects having the _HID
  25. control method.
  26. What: /sys/bus/acpi/devices/.../description
  27. Date: October 2012
  28. Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
  29. Description:
  30. This attribute contains the output of the device object's
  31. _STR control method, if present.
  32. What: /sys/bus/acpi/devices/.../adr
  33. Date: October 2012
  34. Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
  35. Description:
  36. This attribute contains the output of the device object's
  37. _ADR control method, which is present for ACPI device
  38. objects representing devices having standard enumeration
  39. algorithms, such as PCI.
  40. What: /sys/bus/acpi/devices/.../uid
  41. Date: October 2012
  42. Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
  43. Description:
  44. This attribute contains the output of the device object's
  45. _UID control method, if present.
  46. What: /sys/bus/acpi/devices/.../eject
  47. Date: December 2006
  48. Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
  49. Description:
  50. Writing 1 to this attribute will trigger hot removal of
  51. this device object. This file exists for every device
  52. object that has _EJ0 method.
  53. What: /sys/bus/acpi/devices/.../status
  54. Date: Jan, 2014
  55. Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
  56. Description:
  57. (RO) Returns the ACPI device status: enabled, disabled or
  58. functioning or present, if the method _STA is present.
  59. The return value is a decimal integer representing the device's
  60. status bitmap:
  61. =========== ==================================================
  62. Bit [0] Set if the device is present.
  63. Bit [1] Set if the device is enabled and decoding its
  64. resources.
  65. Bit [2] Set if the device should be shown in the UI.
  66. Bit [3] Set if the device is functioning properly (cleared
  67. if device failed its diagnostics).
  68. Bit [4] Set if the battery is present.
  69. Bits [31:5] Reserved (must be cleared)
  70. =========== ==================================================
  71. If bit [0] is clear, then bit 1 must also be clear (a device
  72. that is not present cannot be enabled).
  73. Bit 0 can be clear (not present) with bit [3] set (device is
  74. functional). This case is used to indicate a valid device for
  75. which no device driver should be loaded.
  76. More special cases are covered in the ACPI specification.
  77. What: /sys/bus/acpi/devices/.../hrv
  78. Date: Apr, 2016
  79. Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
  80. Description:
  81. (RO) Allows users to read the hardware version of non-PCI
  82. hardware, if the _HRV control method is present. It is mostly
  83. useful for non-PCI devices because lspci can list the hardware
  84. version for PCI devices.