In computing, the Advanced Configuration and Power Interface (ACPI) specification provides an open standard for unified operating system-centric device configuration and power management. ACPI, first released in December 1996, defines platform-independent interfaces for hardware discovery, configuration, power management and monitoring. The specification is central to Operating System-directed configuration and Power Management (OSPM); a term used to describe a system implementing ACPI, which therefore removes device management responsibilities from legacy firmware interfaces. The standard was originally developed by Intel, Microsoft, and Toshiba, and last published as "Revision 4.0", on June 16, 2009. As of 2009, developers of ACPI also include HP and Phoenix.
ACPI aims to consolidate and improve upon existing power and configuration standards for hardware devices. It provides a transition from existing standards to entirely ACPI-compliant hardware, with some ACPI operating systems already removing support for legacy hardware. With the intention of replacing Advanced Power Management (APM), the MultiProcessor Specification (MPS) and the Plug and Play (PnP) BIOS Specification, the standard brings power management into operating system control (OSPM), as opposed to the previous BIOS central system, which relied on platform-specific firmware to determine power management and configuration policy.
The ACPI specification contains numerous related components for hardware and software programming, as well as a unified standard for device/power interaction and bus configuration. As a document that unifies many previous standards it covers many areas, for system and device builders as well as system programmers. Some software developers have trouble implementing ACPI and express concerns about the requirements that bytecode from an external source must be run by the system with full privileges. Linus Torvalds, creator of the Linux kernel, once described it as "a complete design disaster in every way", in relation to his view that "modern PCs are horrible".
Microsoft Windows 98 was the first operating system with full support for ACPI, with Windows 2000, Windows XP, Windows Vista, Windows 7, FreeBSD, NetBSD, OpenBSD, HP-UX, OpenVMS, Linux and PC versions of SunOS all having at least some support for ACPI.
ACPI requires that once an OSPM-compatible operating system has activated ACPI on a computer, it then takes over and has exclusive control of all aspects of power management and device configuration. The OSPM implementation must expose an ACPI-compatible environment to device drivers, which exposes certain system, device and processor states.
The ACPI specification defines the following seven states (so-called global states) for an ACPI-compliant computer-system:
Furthermore, the specification defines a Legacy state: the state when an operating system runs which does not support ACPI. In this state, the hardware and power are not managed via ACPI, effectively disabling ACPI.
|S0/Working||System is on. The CPU is fully up and running; power conservation operates on a per-device basis.|
|S1 Sleep||System appears off. The CPU is stopped; RAM is refreshed; the system runs in a low power mode.|
|S2 Sleep||System appears off. The CPU has no power; RAM is refreshed; the system uses a lower power mode than S1.|
|S3 Sleep (Standby)||System appears off. The CPU has no power; RAM is in slow refresh; the power supply is in a reduced power mode. This mode is also referred to as 'Save To RAM'.|
|S4 Hibernate||System appears off. The hardware is completely off, but system memory has been saved as a temporary file onto the harddisk. This mode is also referred to as 'Save To Disk'.|
|S5/Off||System is off. The hardware is completely off, the operating system has shut down; nothing has been saved. Requires a complete reboot to return to the Working state.|
The device states D0-D3 are device-dependent:
The CPU power states C0-C3 are defined as follows:
While a device or processor operates (D0 and C0, respectively), it can be in one of several power-performance states. These states are implementation-dependent, but P0 is always the highest-performance state, with P1 to Pn being successively lower-performance states, up to an implementation-specific limit of n no greater than 16.
ACPI-compliant systems interact with hardware through either a "Function Fixed Hardware (FFH) Interface" or a platform-independent hardware programming model which relies on platform-specific AML provided by the Original Equipment Manufacturer.
Function Fixed Hardware interfaces are platform-specific features, provided by platform manufacturers for the purposes of performance and failure recovery. Standard Intel-based PCs have a fixed function interface defined by Intel, which provides a set of core functionality that reduces an ACPI-compliant system's need for full driver stacks for providing basic functionality during boot time or in the case of major system failure.
ACPI defines a large number of tables that provide the interface between an ACPI-compliant operating system and system firmware. These allow description of system hardware in a platform-independent manner, and are presented as either fixed formatted data structures or in ACPI Machine Language (AML). The main AML table is the DSDT (differentiated system description table).
The Root System Description Pointer is located in a platform-dependent manner, and describes the rest of the tables.
|Stable release||20090730 / 2009-07-30|
|License||GNU General Public License|
The ACPI Component Architecture (ACPICA) provides an open-source OS-independent reference implementation of the ACPI specification. ACPICA is written in ANSI C and released as free software under the terms of the GNU General Public License.