Advanced Configuration and Power Interface Specification

Device Configuration
}
Name (_DSD, Package () {
ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
Package () {
Package (2) {"#clock-cells", 0},
Package (2) {"clock-frequency", 120000000}
}
})
Device (SPI0) {
Name (_HID, “PNP####”)
Name (_DSD, Package () {
ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
Package () {
Package (2) {"clocks", Package () {1, ^CLK0}}
}
})
}
}
...
6.2.6 _FIX (Fixed Register Resource Provider)
This optional object is used to provide a correlation between the fixed-hardware register blocks
defined in the FADT and the devices in the ACPI namespace that implement these fixed-hardware
registers. This object evaluates to a package of Plug and Play-compatible IDs (32-bit compressed
EISA type IDs) that correlate to the fixed-hardware register blocks defined in the FADT. The device
under which _FIX appears plays a role in the implementation of the fixed-hardware (for example,
implements the hardware or decodes the hardware’s address). _FIX conveys to OSPM whether a
given device can be disabled, powered off, or should be treated specially by conveying its role in the
implementation of the ACPI fixed-hardware register interfaces. This object takes no arguments.
The _CRS object describes a device’s resources. That _CRS object may contain a superset of the
resources in the FADT, as the device may actually decode resources beyond what the FADT
requires. Furthermore, in a machine that performs translation of resources within I/O bridges, the
processor-relative resources in the FADT may not be the same as the bus-relative resources in the
_CRS.
Arguments:
None
Return Value:
A variable-length Package containing a list of Integers, each containing a PNP ID
Each of fields in the FADT has its own corresponding Plug and Play ID, as shown below:
Version 6.0 301