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