99 lines · plain
1What: /sys/bus/acpi/devices/.../path2Date: December 20063Contact: Rafael J. Wysocki <rjw@rjwysocki.net>4Description:5 This attribute indicates the full path of ACPI namespace6 object associated with the device object. For example,7 \_SB_.PCI0.8 9 This file is not present for device objects representing10 fixed ACPI hardware features (like power and sleep11 buttons).12 13What: /sys/bus/acpi/devices/.../modalias14Date: July 200715Contact: 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 or19 CCCCCCCC contains device object's PNPID (_HID or _CID).20 21What: /sys/bus/acpi/devices/.../hid22Date: April 200523Contact: Rafael J. Wysocki <rjw@rjwysocki.net>24Description:25 This attribute indicates the hardware ID (_HID) of the26 device object. For example, PNP0103.27 This file is present for device objects having the _HID28 control method.29 30What: /sys/bus/acpi/devices/.../description31Date: October 201232Contact: Rafael J. Wysocki <rjw@rjwysocki.net>33Description:34 This attribute contains the output of the device object's35 _STR control method, if present.36 37What: /sys/bus/acpi/devices/.../adr38Date: October 201239Contact: Rafael J. Wysocki <rjw@rjwysocki.net>40Description:41 This attribute contains the output of the device object's42 _ADR control method, which is present for ACPI device43 objects representing devices having standard enumeration44 algorithms, such as PCI.45 46What: /sys/bus/acpi/devices/.../uid47Date: October 201248Contact: Rafael J. Wysocki <rjw@rjwysocki.net>49Description:50 This attribute contains the output of the device object's51 _UID control method, if present.52 53What: /sys/bus/acpi/devices/.../eject54Date: December 200655Contact: Rafael J. Wysocki <rjw@rjwysocki.net>56Description:57 Writing 1 to this attribute will trigger hot removal of58 this device object. This file exists for every device59 object that has _EJ0 method.60 61What: /sys/bus/acpi/devices/.../status62Date: Jan, 201463Contact: Rafael J. Wysocki <rjw@rjwysocki.net>64Description:65 (RO) Returns the ACPI device status: enabled, disabled or66 functioning or present, if the method _STA is present.67 68 The return value is a decimal integer representing the device's69 status bitmap:70 71 =========== ==================================================72 Bit [0] Set if the device is present.73 Bit [1] Set if the device is enabled and decoding its74 resources.75 Bit [2] Set if the device should be shown in the UI.76 Bit [3] Set if the device is functioning properly (cleared77 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 device83 that is not present cannot be enabled).84 85 Bit 0 can be clear (not present) with bit [3] set (device is86 functional). This case is used to indicate a valid device for87 which no device driver should be loaded.88 89 More special cases are covered in the ACPI specification.90 91What: /sys/bus/acpi/devices/.../hrv92Date: Apr, 201693Contact: Rafael J. Wysocki <rjw@rjwysocki.net>94Description:95 (RO) Allows users to read the hardware version of non-PCI96 hardware, if the _HRV control method is present. It is mostly97 useful for non-PCI devices because lspci can list the hardware98 version for PCI devices.99