ACPI 4.0规范最新下载：理解与实践指南

需积分: 12 196 浏览量更新于2024-07-17 收藏 4.18MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

本文档是关于Advanced Configuration and Power Interface (ACPI) 规范的第四版修订，发布日期为2009年6月16日，由Hewlett-Packard Corporation、Intel Corporation、Microsoft Corporation、Phoenix Technologies Ltd. 和 Toshiba Corporation 共同制定。ACPI是一种用于管理和控制现代计算机系统电源管理、配置以及设备驱动程序交互的标准接口，它在个人电脑行业起着至关重要的作用。该规范的目的是为了确保不同硬件厂商生产的设备能够与操作系统（如Microsoft Windows中的Win32、Windows NT等）无缝协作，实现电源管理的高效性和一致性。学习和理解 ACPI 4.0 对于开发者来说至关重要，因为它涉及到Asynchronous System Interface (ASL) 代码的编写，这是一种低级的编程语言，用于描述硬件设备的行为和系统管理策略。在阅读和使用这份规范时，用户需要了解的内容包括但不限于以下几个方面： 1. **架构和术语**：文档详细解释了ACPI的体系结构，包括处理器、内存控制器、电池管理器、散热器和外设等组件如何通过ASL代码进行交互。这包括事件通知机制、状态寄存器管理以及电源状态转换的控制。 2. **ASL语言**：学习ASL编程语言的关键特性，如宏定义、条件语句、循环、函数调用等，这对于编写和调试针对特定硬件平台的ACPI驱动程序至关重要。 3. **硬件兼容性**：理解规范对于硬件制造商的要求，确保设备能与主流操作系统适配，避免因不兼容导致的性能问题或稳定性隐患。 4. **知识产权声明**：在使用ACPI规范时，要清楚地了解版权和使用限制，包括不得用于商业用途或修改而未获得授权，且可能存在对第三方知识产权的潜在侵犯风险。 5. **责任和免责声明**：所有参与制定规范的公司都明确表示，用户在实施规范的过程中可能遇到的问题不承担任何法律责任，包括可能的专利侵权风险。 ACPI 4.0规范是PC系统开发人员必备的学习材料，通过深入研究和实践，能够帮助他们更好地设计和优化系统的电源管理功能，提升用户体验并保持技术的前沿性。对于那些希望深入了解和贡献于这一领域的开发者来说，掌握ASL代码编写是不可或缺的技能。

资源详情

资源推荐

xvi

A.2 Device Power States....................................................................................................................................... 667

A.2.1 Bus Power Management.......................................................................................................................... 668

A.2.2 Display Power Management.................................................................................................................... 668

A.2.3 PCMCIA/PCCARD/CardBus Power Management ................................................................................. 668

A.2.4 PCI Power Management.......................................................................................................................... 668

A.2.5 USB Power Management ........................................................................................................................ 668

A.2.6 Device Classes......................................................................................................................................... 669

A.3 Default Device Class...................................................................................................................................... 669

A.3.1 Default Power State Definitions .............................................................................................................. 669

A.3.2 Default Power Management Policy ......................................................................................................... 669

A.3.3 Default Wake Events............................................................................................................................... 670

A.3.4 Minimum Power Capabilities .................................................................................................................. 670

A.4 Audio Device Class........................................................................................................................................ 670

A.4.1 Power State Definitions ........................................................................................................................... 670

A.4.2 Power Management Policy ...................................................................................................................... 670

A.4.3 Wake Events............................................................................................................................................ 671

A.4.4 Minimum Power Capabilities .................................................................................................................. 671

A.5 COM Port Device Class ................................................................................................................................ 671

A.5.1 Power State Definitions ........................................................................................................................... 672

A.5.2 Power Management Policy ...................................................................................................................... 672

A.5.3 Wake Events............................................................................................................................................ 672

A.5.4 Minimum Power Capabilities .................................................................................................................. 672

A.6 Display Device Class...................................................................................................................................... 672

A.6.1 Power State Definitions ........................................................................................................................... 673

A.6.2 Power Management Policy for the Display Class.................................................................................... 678

A.6.3 Wake Events............................................................................................................................................ 679

A.6.4 Minimum Power Capabilities .................................................................................................................. 679

A.6.5 Performance States for Display Class Devices ........................................................................................ 679

A.7 Input Device Class......................................................................................................................................... 681

A.7.1 Power State Definitions ........................................................................................................................... 681

A.7.2 Power Management Policy ...................................................................................................................... 681

A.7.3 Wake Events............................................................................................................................................ 682

A.7.4 Minimum Power Capabilities .................................................................................................................. 682

A.8 Modem Device Class ..................................................................................................................................... 682

A.8.1 Technology Overview ............................................................................................................................. 682

A.8.2 Power State Definitions ........................................................................................................................... 683

A.8.3 Power Management Policy ...................................................................................................................... 684

A.8.4 Wake Events............................................................................................................................................ 684

A.8.5 Minimum Power Capabilities .................................................................................................................. 684

A.9 Network Device Class.................................................................................................................................... 685

A.9.1 Power State Definitions ........................................................................................................................... 685

A.9.2 Power Management Policy ...................................................................................................................... 686

A.9.3 Wake Events............................................................................................................................................ 686

A.9.4 Minimum Power Capabilities .................................................................................................................. 686

A.10 PC Card Controller Device Class............................................................................................................... 686

A.10.1 Power State Definitions ......................................................................................................................... 687

A.10.2 Power Management Policy .................................................................................................................... 688

A.10.3 Wake Events.......................................................................................................................................... 688

A.10.4 Minimum Power Capabilities ................................................................................................................ 688

A.11 Storage Device Class ................................................................................................................................... 689

A.11.1 Power State Definitions ......................................................................................................................... 689

A.11.2 Power Management Policy .................................................................................................................... 690

A.11.3 Wake Events.......................................................................................................................................... 690

A.11.4 Minimum Power Capabilities ................................................................................................................ 690

Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba

xvii

Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba

B ACPI EXTENSIONS FOR DISPLAY ADAPTERS........................................................................ 691

B.1 Introduction ................................................................................................................................................... 691

B.2 Definitions ...................................................................................................................................................... 692

B.3 ACPI Namespace........................................................................................................................................... 692

B.4 Display-specific Methods............................................................................................................................... 693

B.4.1 _DOS (Enable/Disable Output Switching)............................................................................................... 693

B.4.2 _DOD (Enumerate All Devices Attached to the Display Adapter).......................................................... 694

B.4.3 _ROM (Get ROM Data) .......................................................................................................................... 697

B.4.4 _GPD (Get POST Device) ....................................................................................................................... 698

B.4.5 _SPD (Set POST Device) ........................................................................................................................ 698

B.4.6 _VPO (Video POST Options).................................................................................................................. 699

B.5 Notifications for Display Devices.................................................................................................................. 699

B.6 Output Device-specific Methods................................................................................................................... 699

B.6.1 _ADR (Return the Unique ID for this Device) ........................................................................................ 700

B.6.2 _BCL (Query List of Brightness Control Levels Supported)................................................................... 700

B.6.3 _BCM (Set the Brightness Level)............................................................................................................ 700

B.6.4 _BQC (Brightness Query Current level).................................................................................................. 701

B.6.5 _DDC (Return the EDID for this Device)................................................................................................ 701

B.6.6 _DCS (Return the Status of Output Device) ............................................................................................ 701

B.6.7 _DGS (Query Graphics State).................................................................................................................. 702

B.6.8 _DSS (Device Set State) .......................................................................................................................... 702

B.7 Notifications Specific to Output Devices...................................................................................................... 703

B.8 Notes on State Changes................................................................................................................................. 704

INDEX....................................................................................................................................................... 706

Introduction 19

1 Introduction

The Advanced Configuration and Power Interface (ACPI) specification was developed to establish industry

common interfaces enabling robust operating system (OS)-directed motherboard device configuration and

power management of both devices and entire systems. ACPI is the key element in Operating System-

directed configuration and Power Management (OSPM).

ACPI evolved the existing pre-ACPI collection of power management BIOS code, Advanced Power

Management (APM) application programming interfaces (APIs, PNPBIOS APIs, Multiprocessor

Specification (MPS) tables and so on into a well-defined power management and configuration interface

specification. ACPI provides the means for an orderly transition from existing (legacy) hardware to ACPI

hardware, and it allows for both ACPI and legacy mechanisms to exist in a single machine and to be used

as needed.

Further, system architectures being built at the time of the original ACPI specification’s inception,

stretched the limits of historical “Plug and Play” interfaces. ACPI evolved existing motherboard

configuration interfaces to support advanced architectures in a more robust, and potentially more efficient

manner.

The interfaces and OSPM concepts defined within this specification are suitable to all classes of computers

including (but not limited to) desktop, mobile, workstation, and server machines. From a power

management perspective, OSPM/ACPI promotes the concept that systems should conserve energy by

transitioning unused devices into lower power states including placing the entire system in a low-power

state (sleeping state) when possible.

This document describes ACPI hardware interfaces, ACPI software interfaces and ACPI data structures

that, when implemented, enable support for robust OS-directed configuration and power management

(OSPM).

1.1 Principal Goals

ACPI is the key element in implementing OSPM. ACPI-defined interfaces are intended for wide adoption

to encourage hardware and software vendors to build ACPI-compatible (and, thus, OSPM-compatible)

implementations.

The principal goals of ACPI and OSPM are to:

1. Enable all computer systems to implement motherboard configuration and power management

functions, using appropriate cost/function tradeoffs.

 Computer systems include (but are not limited to) desktop, mobile, workstation, and server

machines.

 Machine implementers have the freedom to implement a wide range of solutions, from the very

simple to the very aggressive, while still maintaining full OS support.

 Wide implementation of power management will make it practical and compelling for applications

to support and exploit it. It will make new uses of PCs practical and existing uses of PCs more

economical.

2. Enhance power management functionality and robustness.

 Power management policies too complicated to implement in a ROM BIOS can be implemented

and supported in the OS, allowing inexpensive power managed hardware to support very elaborate

power management policies.

 Gathering power management information from users, applications, and the hardware together

into the OS will enable better power management decisions and execution.

 Unification of power management algorithms in the OS will reduce conflicts between the

firmware and OS and will enhance reliability.

3. Facilitate and accelerate industry-wide implementation of power management.

 OSPM and ACPI reduces the amount of redundant investment in power management throughout

the industry, as this investment and function will be gathered into the OS. This will allow industry

participants to focus their efforts and investments on innovation rather than simple parity.

Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba

20 Advanced Configuration and Power Interface Specification

 The

OS can evolve independently of the hardware, allowing all ACPI-compatible machines to

gain the benefits of OS improvements and innovations.

4. Create a robust interface for configuring motherboard devices.

 Enable new advanced designs not possible with existing interfaces.

1.2 Power Management Rationale

It is necessary to move power management into the OS and to use an abstract interface (ACPI) between the

OS and the hardware to achieve the principal goals set forth above.

 Minimal support for power management inhibits application vendors from supporting or

exploiting it.



machine on w

from machin

on all OSPM



to their produ



and hardware

OS can have

word process when

the required

required devi

lazy I/O requ

requires know ,

and being ab



decision Fo

for incoming

telephone in

deepest sleep

 BIOS co ork



man



between the



mobile s e



therefore che

 The xis

likewise, the

Moving power management functionality into the OS makes it available on every

hich the OS is installed. The level of functionality (power savings, and so on) varies

e to machine, but users and applications will see the same power interfaces and semantics

machines.

This will enable application vendors to invest in adding power management functionality

cts.

 Legacy power management algorithms were restricted by the information available to the BIOS

that implemented them. This limited the functionality that could be implemented.

Centralizing power management information and directives from the user, applications,

in the OS allows the implementation of more powerful functionality. For example, an

a policy of dividing I/O operations into normal and lazy. Lazy I/O operations (such as a

or saving files in the background) would be gathered up into clumps and done only

I/O device is powered up for some other reason. A non-lazy I/O request made when the

ce was powered down would cause the device to be powered up immediately, the non-

est to be carried out, and any pending lazy I/O operations to be done. Such a policy

ing when I/O devices are powered up, knowing which application I/O requests are lazy

le to assure that such lazy I/O operations do not starve.

Appliance functions, such as answering machines, require globally coherent power

s. r example, a telephone-answering application could call the OS and assert, “I am waiting

phone calls; any sleep state the system enters must allow me to wake and answer the

1 second.” Then, when the user presses the “off” button, the system would pick the

state consistent with the needs of the phone answering service.

de has become very complex to deal with power management. It is difficult to make w

OS and is limited to static cwith an onfigurations of the hardware.

There is much less state information for the BIOS to retain and manage (because the OS

ages it).

Power management algorithms are unified in the OS, yielding much better integration

OS and the hardware.

Because additional ACPI tables (Definition Blocks) can be loaded, for example, when a

yst m docks, the OS can deal with dynamic machine configurations.

Because the BIOS has fewer functions and they are simpler, it is much easier (and

aper) to implement and support.

e ting structure of the PC platform constrains OS and hardware designs.

 Because ACPI is abstract, the OS can evolve separately from the hardware and,

hardware from the OS.

 ACPI is by nature more portable across operating systems and processors. ACPI control metho

allow for very flexible implementations of particular features.

Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba

剩余726页未读，继续阅读

shaqidaxi

粉丝: 1
资源: 1

ACPI 4.0规范最新下载：理解与实践指南

ACPI 5.0 spec

ACPI 驱动！XP Win7

Server2008R2上简单配置iSCSI

acpispec下载

acpi_spec_6_5_aug29

Linux怎么控制ACPI

acpi规范20201006release 6.3

ACPI事件类型有哪些？

acpi kernel编译

ACPI APEI的细节

ubuntu安装acpi error

linux kernel怎么查找ACPI Table

linux内核怎么修改acpi表

装linux系统出现acpi bios error

linux驱动中，从ACPI表内读取数据

《uefi内核导读》之acpi编程入门

acpi-tools离线包

Linux的ACPI在那里配置

终止代码ACPI BIOS

X86的Tpm20Acpi

最新资源