27.10.2015 Views

Advanced Configuration and Power Interface Specification

ACPI_6.0

ACPI_6.0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Advanced</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Power</strong> <strong>Interface</strong> <strong>Specification</strong><br />

9.16.3 User Presence Sensor Events<br />

To communicate changes in user presence to OSPM, AML code should issue a<br />

Notify(upd_device, 0x80) whenever a change in user presence has occurred. The OS<br />

receives this notification <strong>and</strong> calls the _UPD control method to determine the current user presence<br />

status.<br />

UPD notifications should be generated whenever a transition occurs between one of the user<br />

presence states (absent, present, or unknown) – but at a level of granularity that provides an<br />

appropriate response without overly taxing the system with unnecessary interrupts.<br />

9.17 I/O APIC Device<br />

This optional device describes a discrete I/O APIC device that is not bus enumerated (e.g., as a PCI<br />

device). Describing such a device in the ACPI namespace is only necessary if hot plug of this device<br />

is supported. If hot plug of this device is not supported, an MADT I/O APIC (Section 5.2.12.3,”I/O<br />

APIC Structure”) entry or I/O SAPIC (Section 5.2.12.9, “I/O SAPIC Structure”) entry is sufficient<br />

to describe this device.<br />

An I/O APIC device is an I/O unit that complies with either of the APIC interrupt models supported<br />

by ACPI. These interrupt models are described Section 5.2.12.3,”I/O APIC Structure” <strong>and</strong><br />

Section 5.2.12.9,”I/O SAPIC Structure”. If the device is an I/O unit that complies with the APIC<br />

interrupt model, it is declared using the ACPI000A identifier. If this device is an I/O unit that<br />

complies with the SAPIC interrupt model, it is declared using the ACPI000B identifier. If this device<br />

complies with both the APIC <strong>and</strong> SAPIC interrupt models (I/OxAPIC), it is declared using the<br />

ACPI0009 identifier.<br />

An I/O APIC device declared using any of the above identifiers must contain a _GSB object as<br />

defined inSection 6.2.7, “_GSB (Global System Interrupt Base)” to report its Global System<br />

Interrupt Base. It must also contain a _CRS object that reports the base address of the I/O APIC<br />

device. The _CRS object is required to contain only one resource, a memory resource pointing to the<br />

I/O APIC register base.<br />

Note: Because the _CRS <strong>and</strong> _GSB methods provide sufficient information, it is not necessary to<br />

provide _MAT under an I/O APIC device.<br />

For an I/O APIC device that is described both in the MADT <strong>and</strong> in the namespace, the base address<br />

described in the MADT entry must be the same as the base address in the IO APIC device _CRS at<br />

boot time. OSPM must use the information from the MADT until such a time as the _CRS <strong>and</strong><br />

_GSB methods in the namespace device can be processed. At this point OSPM must ignore the<br />

MADT entry.<br />

9.18 Time <strong>and</strong> Alarm Device<br />

The following sections define the operation <strong>and</strong> definition of the optional control method-based<br />

Time <strong>and</strong> Alarm device, which provides a hardware independent abstraction <strong>and</strong> a more robust<br />

alternative to the Real Time Clock (RTC), See Section 9.15, "PC/AT RTC/CMOS Devices".<br />

The time capabilities of the time <strong>and</strong> alarm device maintain the time of day information across<br />

platform power transitions, <strong>and</strong> keep track of time even when the platform is turned off. It is<br />

538 April, 2015 Version 6.0

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!