Advanced Configuration and Power Interface Specification

Advanced Configuration and Power Interface Specification
Scope(\_SB) {
Device(PCI0) { // Root PCI Bus
Name(_HID, EISAID("PNP0A03")) // Need _HID for root device
Name(_ADR,0) // Device 0 on this bus
Method (_CRS,0){ // Need current resources for root device
// Return current resources for root bridge 0
}
Name(_PRT, Package(){ // Need PCI IRQ routing for PCI bridge
// Package with PCI IRQ routing table information
})
Name(_FIX, Package(1) {
EISAID("PNP0C25")} // PM2 control ID
)
Device (PX40) { // ISA
Name(_ADR,0x00070000)
Name(_FIX, Package(1) {
EISAID("PNP0C20")} // SMI command port
)
Device (NS17) { // NS17 (Nat. Semi 317, an ACPI part)
Name(_HID, EISAID("PNP0C02"))
Name(_FIX, Package(3) {
EISAID("PNP0C22"), // PM1b event ID
EISAID("PNP0C24"), // PM1b control ID
EISAID("PNP0C28")} // GPE1 ID
}
} // end PX40
Device (PX43) { // PM Control
Name(_ADR,0x00070003)
Name(_FIX, Package(4) {
EISAID("PNP0C21"), // PM1a event ID
EISAID("PNP0C23"), // PM1a control ID
EISAID("PNP0C26"), // PM Timer ID
EISAID("PNP0C27")} // GPE0 ID
)
} // end PX43
} // end PCI0
} // end scope SB
6.2.6 _GSB (Global System Interrupt Base)
_GSB is an optional object that evaluates to an integer that corresponds to the Global System
Interrupt Base for the corresponding I/O APIC device. The I/O APIC device may either be bus
enumerated (e.g. as a PCI device) or enumerated in the namespace as described in Section 9.17,”I/O
APIC Device”. Any I/O APIC device that either supports hot-plug or is not described in the MADT
must contain a _GSB object.
If the I/O APIC device also contains a _MAT object, OSPM evaluates the _GSB object first before
evaluating the _MAT object. By providing the Global System Interrupt Base of the I/O APIC, this
object enables OSPM to process only the _MAT entries that correspond to the I/O APIC device. See
Section 6.2.9, “_MAT (Multiple APIC Table Entry)”. Since _MAT is allowed to potentially return
all the MADT entries for the entire platform, _GSB is needed in the I/O APIC device scope to enable
OSPM to identify the entries that correspond to that device.
If an I/O APIC device is activated by a device-specific driver, the physical address used to access the
I/O APIC will be exposed by the driver and cannot be determined from the _MAT object. In this
Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba 273