Lines Matching full:acpi
5 ACPI Device Tree - Representation of ACPI Namespace
17 The Linux ACPI subsystem converts ACPI namespace objects into a Linux
19 receiving ACPI hotplug notification events. For each device object
21 /sys/bus/acpi/devices.
23 This document illustrates the structure of the ACPI device tree.
25 ACPI Definition Blocks
28 The ACPI firmware sets up RSDP (Root System Description Pointer) in the
30 Description Table). The XSDT always points to the FADT (Fixed ACPI
32 includes various fixed-length entries that describe fixed ACPI features
39 blocks that contain definitions of various objects, including ACPI
40 control methods, encoded in AML (ACPI Machine Language). The data block
42 data structure called the ACPI namespace whose topology reflects the
45 The relationships between ACPI System Definition Tables described above
69 | ACPI Namespace |
72 Figure 1. ACPI Definition Blocks
76 compatibility with ACPI 1.0 operating systems. The OS is expected
80 Example ACPI Namespace
85 The following naming conventions apply to object names in the ACPI
92 4. Names starting with '_' are reserved by the ACPI specification.
99 The figure below shows an example ACPI namespace::
189 Figure 2. Example ACPI Namespace
192 Linux ACPI Device Objects
195 The Linux kernel's core ACPI subsystem creates struct acpi_device
196 objects for ACPI namespace objects representing devices, power resources
200 ACPI namespace representation of the given object and 'instance' is used
233 Table 1. ACPI Namespace Objects Mapping
236 the basis of the contents of ACPI System Description Tables (as
241 The object's source is an ACPI namespace node (as indicated by the
251 The struct acpi_device object is created for an ACPI namespace node
252 with specific control methods (as indicated by the ACPI defined
255 example, if the _BCL method is present for an ACPI namespace node, a
259 The third column of the above table indicates which ACPI System
270 the corresponding ACPI namespace node. The object's sysfs directory
280 ACPI namespace node, although that object represents a device (for
286 Linux ACPI Physical Device Glue
289 ACPI device (i.e. struct acpi_device) objects may be linked to other
292 the ACPI device object is a "companion" of a device otherwise
295 (2) to do specific things to the device with the help of its ACPI
296 control methods. One ACPI device object may be linked this way to
299 If an ACPI device object is linked to a "physical" device, its sysfs
303 the sysfs directory of the companion ACPI device object.
305 ACPI namespace. For example, if there's an ACPI namespace object
306 representing a PCI device (i.e. a device object under an ACPI namespace
309 representing the struct acpi_device object created for that ACPI
315 implementation is located in the drivers/acpi/glue.c file, but there are
318 drivers/pci/pci-acpi.c.
321 Example Linux ACPI Device Tree
325 example ACPI namespace illustrated in Figure 2 with the addition of
329 | LNXSYSTM:00 | \ | acpi:LNXSYSTM: |
333 +-| LNXPWRBN:00 | N/A | acpi:LNXPWRBN: |
337 +-| LNXSLPBN:00 | N/A | acpi:LNXSLPBN: |
341 +-| LNXCPU:00 | \_PR_.CPU0 | acpi:LNXCPU: |
345 +-| LNXSYBUS:00 | \_SB_ | acpi:LNXSYBUS: |
349 | +-| PNP0C0D:00 | \_SB_.LID0 | acpi:PNP0C0D: |
353 | +-| PNP0A08:00 | \_SB_.PCI0 | acpi:PNP0A08:PNP0A03: |
361 | | +-| LNXPOWER:00 | \_SB_.PCI0.RP03.PXP3 | acpi:LNXPOWER: |
365 | +-| LNXVIDEO:00 | \_SB_.PCI0.GFX0 | acpi:LNXVIDEO: |
373 +-| LNXSYBUS:01 | \_TZ_ | acpi:LNXSYBUS: |
377 +-| LNXPOWER:0a | \_TZ_.FN00 | acpi:LNXPOWER: |
381 +-| PNP0C0B:00 | \_TZ_.FAN0 | acpi:PNP0C0B: |
385 +-| LNXTHERM:00 | \_TZ_.TZ00 | acpi:LNXTHERM: |
388 Figure 3. Example Linux ACPI Device Tree
393 2. 'path' is the ACPI namespace path of the corresponding
394 ACPI namespace object, as returned by the object's 'path'