LLMpediaThe first transparent, open encyclopedia generated by LLMs

Advanced Configuration and Power Interface

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: ChromeOS Hop 4
Expansion Funnel Raw 53 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted53
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
Advanced Configuration and Power Interface
NameAdvanced Configuration and Power Interface
AbbreviationACPI
DeveloperIntel Corporation, Microsoft, Toshiba Corporation
First release1996
Latest release6.5

Advanced Configuration and Power Interface is a specification for power management and hardware configuration that defines interfaces between operating systems and platform firmware. It unifies legacy approaches from Intel Corporation, Microsoft, and Toshiba Corporation while impacting implementations across AMD, ARM Holdings, Dell Technologies, Hewlett-Packard, and Lenovo. The specification influences system firmware, motherboard vendors, and operating systems such as Microsoft Windows, Linux (kernel), and FreeBSD.

Overview

The specification emerged from cooperation among Intel Corporation, Microsoft, Toshiba Corporation, Compaq, and Phoenix Technologies to replace legacy standards including Advanced Power Management and to align with trends driven by Intel 386, Pentium, Itanium, and later x86-64 platforms. ACPI defines standardized mechanisms implemented in BIOS, UEFI, and firmware by vendors like American Megatrends, Insyde Software, and Acer Inc. for operating systems including Microsoft Windows, Linux (kernel), FreeBSD, NetBSD, and OpenBSD. Adoption affected hardware designers at ASUS, Gigabyte Technology, MSI, and server OEMs such as IBM and Hewlett-Packard Enterprise.

Architecture and Components

ACPI’s architecture specifies tables, method execution environments, and namespace semantics for power and configuration management used by firmware from AMI, Phoenix Technologies, and Insyde Software. Core components interact with chipset features from Intel Corporation, AMD, and NVIDIA, and with platform resource allocation frameworks in Microsoft Windows, Linux (kernel), and virtualization platforms like VMware, Xen (software), and KVM. The ACPI Machine Language (AML) bytecode is produced by compilers such as those originating from Intel Corporation and tools used by vendors including Toshiba Corporation and Compaq. System integrators including Dell Technologies, Lenovo, and Apple Inc. map ACPI-defined power states to platform capabilities of processors like Intel Core, AMD Ryzen, and ARM Cortex-A.

ACPI Tables and Data Structures

The specification defines multiple tables—most notably the RSDP, RSDT/XSDT, FADT, DSDT, SSDTs, and FACS—implemented by firmware from American Megatrends, Phoenix Technologies, and Insyde Software. These tables describe namespace objects, methods, and device descriptors referenced by operating systems including Microsoft Windows, Linux (kernel), FreeBSD, OpenBSD, and NetBSD. Compiler and decompiler tools arise from projects associated with Intel Corporation, ACPI Component Architecture, and community projects used by Debian, Ubuntu, and Red Hat Enterprise Linux. Hardware platforms from ASUS, Gigabyte Technology, MSI, and server lines by Dell Technologies and Hewlett-Packard Enterprise rely on correct table construction to interoperate with drivers in Microsoft Windows Driver Model, Linux kernel driver model, and virtualization stacks such as QEMU.

Power Management and States

ACPI formalizes global power states (G0/G1/G2/G3), processor performance states (P-states), and idle states (C-states) used by CPUs from Intel Corporation, AMD, and ARM Holdings. It standardizes device states (D0–D3) for peripherals from vendors like Intel Corporation, NVIDIA, Broadcom, and Realtek Semiconductor and integrates battery and thermal management interfaces used in laptops by Dell Technologies, Lenovo, and Apple Inc.. Operating systems including Microsoft Windows, Linux (kernel), and FreeBSD map system suspend and hibernation semantics to implementation features like S3 (suspend to RAM), S4 (hibernate), and S5 (soft off), coordinating with platform controllers such as Intel Power Controller and embedded controllers designed by Microchip Technology.

Device Configuration and Hotplugging

ACPI provides mechanisms for device enumeration, resource negotiation, and runtime power management for hotpluggable buses like PCI Express, USB, and legacy PCI supported by hardware vendors including Intel Corporation, AMD, NVIDIA, and Texas Instruments. Firmware tables enumerate devices for operating systems such as Microsoft Windows and distributions like Ubuntu, Fedora, and Debian GNU/Linux. Hotplug events are mediated through ACPI methods and notifications, integrating with kernel subsystems in the Linux kernel, device frameworks in Microsoft Windows, and virtualization features in Xen (software), KVM, and VMware ESXi.

BIOS/OS Interaction and Implementation

ACPI mediates BIOS/UEFI firmware produced by American Megatrends, Phoenix Technologies, Insyde Software, and platform vendors like Dell Technologies, Lenovo, and HP Inc. with operating systems including Microsoft Windows, Linux (kernel), FreeBSD, OpenBSD, and NetBSD. The specification defines AML execution environments and control methods consumed by operating system components such as Windows NT kernel, Linux kernel, and firmware interfaces used by UEFI Forum. Implementations require collaboration with driver ecosystems including Microsoft Windows Driver Model, Linux kernel driver model, and third-party projects in distributions like Red Hat Enterprise Linux, SUSE, and Canonical (company)-based releases.

Security, Issues, and Compatibility

ACPI’s complexity has led to security concerns, firmware bugs, and compatibility challenges across platforms from Intel Corporation, AMD, ARM Holdings, Dell Technologies, and Lenovo. Vulnerabilities have been addressed by vendors including Microsoft, Intel Corporation, and AMD and discussed in security forums and incident responses involving organizations like CERT Coordination Center and Open Web Application Security Project. Community projects including COREBOOT and kernel maintainers for Linux (kernel) and FreeBSD perform table fixes and ACPI overrides; distributions such as Debian, Fedora, and Ubuntu ship kernel patches and workarounds. Compatibility testing involves standards bodies such as the UEFI Forum and industry consortia including PCI-SIG.

Category:Computer power management standards