Lines Matching refs:of

1 ACPI Device Tree - Representation of ACPI Namespace
14 This document illustrates the structure of the ACPI device tree.
30 of the hardware. The FADT contains a pointer to the DSDT
36 blocks that contain definitions of various objects, including ACPI
38 of the DSDT along with the contents of SSDTs represents a hierarchical
40 structure of the underlying hardware platform.
80 is a hierarchy of objects identified by names and paths.
84 2. The first byte of a name must be one of 'A' - 'Z', '_'.
85 3. Each of the remaining bytes of a name must be one of 'A' - 'Z', '0'
88 5. The '\' symbol represents the root of the namespace (i.e. names
90 6. The '^' symbol represents the parent of the current namespace node
91 (i.e. names prepended with '^' are relative to the parent of the
193 format of their names is <bus_id:instance>, where 'bus_id' refers to the
194 ACPI namespace representation of the given object and 'instance' is used
195 for distinguishing different object of the same 'bus_id' (it is
196 two-digit decimal representation of an unsigned integer).
198 The value of 'bus_id' depends on the type of the object whose name it is
199 part of as listed in the table below.
230 the basis of the contents of ACPI System Description Tables (as
232 second column of the table above):
252 The third column of the above table indicates which ACPI System
253 Description Tables contain information used for the creation of the
257 The forth column of the above table indicates the 'bus_id' generation
258 rule of the struct acpi_device object:
260 _HID in the last column of the table means that the object's bus_id
264 used to retrieve the _HID and _CIDs of that object.
267 objects having bus_id of the "LNXxxxxx" form (pseudo devices), in
270 'device' in the last column of the table indicates that the object's
271 bus_id cannot be determined from _HID/_CID of the corresponding
283 the ACPI device object is a "companion" of a device otherwise
286 (2) to do specific things to the device with the help of its ACPI
292 directory of the target device object. In turn, the target device's
294 the sysfs directory of the companion ACPI device object.
299 bus number of the parent PCI bridge is 0, the sysfs directory
302 /sys/devices/pci0000:00/0000:00:02:0/ sysfs directory of the
305 The linking mechanism is generally bus-specific. The core of its
308 elsewhere. For example, the PCI-specific part of it is located in
314 The sysfs hierarchy of struct acpi_device objects corresponding to the
315 example ACPI namespace illustrated in Figure 2 with the addition of
381 1. 'object' is the name of the object's directory in sysfs.
382 2. 'path' is the ACPI namespace path of the corresponding
385 3. 'modalias' is the value of the object's 'modalias' sysfs