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.

ACPI Hardware <strong>Specification</strong><br />

4<br />

ACPI Hardware <strong>Specification</strong><br />

ACPI defines st<strong>and</strong>ard interface mechanisms that allow an ACPI-compatible OS to control <strong>and</strong><br />

communicate with an ACPI-compatible hardware platform. These interface mechanisms are<br />

optional (See "Hardware-Reduced ACPI", below).However, if the ACPI Hardware <strong>Specification</strong> is<br />

implemented, platforms must comply with the requirements in this section.<br />

This section describes the hardware aspects of ACPI.<br />

ACPI defines “hardware” as a programming model <strong>and</strong> its behavior. ACPI strives to keep much of<br />

the existing legacy programming model the same; however, to meet certain feature goals, designated<br />

features conform to a specific addressing <strong>and</strong> programming scheme. Hardware that falls within this<br />

category is referred to as “fixed.”<br />

Although ACPI strives to minimize these changes, hardware engineers should read this section<br />

carefully to underst<strong>and</strong> the changes needed to convert a legacy-only hardware model to an ACPI/<br />

Legacy hardware model or an ACPI-only hardware model.<br />

ACPI classifies hardware into two categories: Fixed or Generic. Hardware that falls within the fixed<br />

category meets the programming <strong>and</strong> behavior specifications of ACPI. Hardware that falls within<br />

the generic category has a wide degree of flexibility in its implementation.<br />

4.1 Hardware-Reduced ACPI<br />

For certain classes of systems the ACPI Hardware <strong>Specification</strong> may not be adequate. Examples<br />

include legacy-free, UEFI-based platforms with recent processors, <strong>and</strong> those implementing mobile<br />

platform architectures. For such platforms, a Hardware-reduced ACPI mode is defined. Under this<br />

definition, the ACPI Fixed Hardware interface is not implemented, <strong>and</strong> software alternatives for<br />

many of the features it supports are used instead. Note, though, that Hardware-reduced ACPI is not<br />

intended to support every possible ACPI system that can be built today. Rather, it is intended to<br />

introduce new systems that are designed to be HW-reduced from the start. The ACPI HW<br />

<strong>Specification</strong> should be used if the platform cannot be designed to work without it. Specifically, the<br />

following features are not supported under the HW-reduced definition:<br />

• The Global Lock, SMI_CMD, ACPI Enable <strong>and</strong> ACPI Disable. Hardware-reduced ACPI<br />

systems always boot in ACPI mode, <strong>and</strong> do not support hardware resource sharing between<br />

OSPM <strong>and</strong> other asynchronous operating environments, such as UEFI Runtime Services or<br />

System Management Mode.<br />

• Bus Master Reload <strong>and</strong> Arbiter Disable. Systems that depend on OS use of these bits to maintain<br />

cache coherency across processor sleep states are not supported.<br />

• GPE block devices are not supported.<br />

Platforms that require the above features must implement the ACPI Hardware <strong>Specification</strong>.<br />

Platforms that are designed for the Hardware-reduced ACPI definition must implement Revision 5<br />

or greater of the Fixed ACPI Descriptor Table, <strong>and</strong> must set the HW_REDUCED_ACPI flag in the<br />

Flags field.<br />

Version 6.0 57

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

Saved successfully!

Ooh no, something went wrong!