Advanced Configuration and Power Interface

All you want to know about Advanced Configuration and Power Interface

This article or section includes a list of references or external links, but its sources remain unclear because it has insufficient inline citations.
You can improve this article by introducing more precise citations where appropriate. (June 2008)

This article or section needs copy editing for grammar, style, cohesion, tone or spelling.
You can assist by editing it now. A how-to guide is available. (June 2008)

The Advanced Configuration and Power Interface (ACPI) specification is an open standard, for unified, operating system-centic 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 and therefore removing device management from legacy firmware interfaces. The standard was developed by HP, Intel, Microsoft, Phoenix, Toshiba, and Dell, and last published as "Revision 3.0b", on October 10, 2006.^[1]

1 Overview
2 OSPM Responsibilities
3 Hardware Interface
4 Firmware Interface
5 ACPI Component Architecture (ACPICA)
6 See also
7 References
8 External links

Overview

The standard was an attempt to bring together and improve on existing device power and configuration standards.^[1] It provides a transition from previous interfaces to entirely ACPI hardware, with compliant operating systems already removing support for legacy hardware^[2]. Advanced Power Management, the Multi-processor Specification and the Plug and Play BIOS Specification were the primary standards intended for replacement by the specification.^[3] This transition brings Power Management into operating system control (OSPM), as opposed to the previous BIOS central system, which relied on platform specific firmware.^[4]

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. The document which unifies many previous standards, therefore covers many areas, for system and device builders as well as system programmers. Some software developers have trouble^[5] implementing ACPI and concerns have been expressed about the requirements that operating systems have to run external bytecode with full privileges.

Windows 98 was the first Microsoft OS to support ACPI. FreeBSD, Linux, NetBSD and OpenBSD all have at least some support for ACPI.

OSPM Responsibilities

Operating System-directed configuration and power management requires that once a compatible operating system takes over power management and device configuration reponsibilities from any existing standard implementations that it has exclusive control of all aspects. The OSPM implementation must define an ACPI compatible enviroment to Device Drivers, which exposes certain System, Device and Processor states.

Power States

System states

The ACPI specification defines the following seven states (so-called global states) which an ACPI-compliant computer system can be in:

G0 (S0) Working
G1 Sleeping subdivides into the four states S1 through S4.
- S1: All processor caches are flushed, and the CPU(s) stop executing instructions. Power to the CPU(s) and RAM is maintained; devices that do not indicate they must remain on may be powered down.
- S2: The CPU is powered off.
- S3: Commonly referred to as Standby or Sleep. RAM is still powered.
- S4: Hibernation. All content of main memory is saved to non-volatile memory such as a hard drive, and is powered down.
G2 (S5) Soft Off-- G2, S5, and Soft Off are synonyms. G2 is almost the same as G3 Mechanical Off, but some components remain powered so the computer can "wake" from input from the keyboard, clock, modem, LAN, or USB device.^[6]
G3 Mechanical Off: The computer's power consumption approaches close to zero, to the point that the power cord can be removed and the system is safe for disassembly (typically, only the real-time clock is running off its own small battery).

Furthermore, a state Legacy is defined as 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.

Device states

The device states D0-D3 are device-dependent:

D0 Fully-On is the operating state.
D1 and D2 are intermediate power-states whose definition varies by device.
D3 Off has the device powered off and unresponsive to its bus.

Processor states

The CPU power states C0-C3 are defined as follows:

C0 is the operating state.
C1 (often known as Halt) is a state where the processor is not executing instructions, but can return to an executing state essentially instantaneously. Some processors, such as the Pentium 4, also support an Enhanced C1 state (C1E) for lower power consumption.
C2 (often known as Stop-Clock) is a state where the processor maintains all software-visible state, but may take longer to wake up.
C3 (often known as Sleep) is a state where the processor does not need to keep its cache coherent, but maintains other state. Some processors have variations on the C3 state (Deep Sleep, Deeper Sleep, etc.) that differ in how long it takes to wake the processor.

Performance states

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.

P-states have become known as SpeedStep in Intel processors, PowerNow! or Cool'n'Quiet in AMD processors and PowerSaver in VIA processors.

Hardware Interface

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^[7], which provides a set of core functionality that reduces a ACPI-compliant systems need for full driver stacks for providing basic functionality during boot time or in the case of major system failure.

Firmware Interface

Please wikify this article or section.
Help improve this article by adding relevant internal links. (September 2008)

ACPI defines a large number of tables that provide the interface between an ACPI compliant operating system and system firmware. That allow description of system hardware in a platform-independent manner, and are presented as either fixed formatted data structures or in ACPI Machine Language.

The Root System Description Pointer is located in a platform dependent manner, and goes on to describe the rest of the tables.

ACPI Component Architecture (ACPICA)

Please help improve this section by expanding it. Further information might be found on the talk page or at requests for expansion. (July 2008)

The ACPI Component Architecture (ACPICA) is an open source OS-independent reference implementation of the ACPI specification.^[8] ACPICA is written in ANSI C.

References

External links

This article was originally based on material from the Free On-line Dictionary of Computing, which is licensed under the GFDL.

Retrieved from "http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface"

No comments have been added.

Your name:
City:
Country:
Your comments:

Security check * (Please enter the number into adjoining box)

up to content »