没有合适的资源?快使用搜索试试~ 我知道了~
首页ACPI 3.0a高级电源管理接口标准详解
ACPI(Advanced Configuration and Power Interface,高级配置与电源接口)是一项重要的技术标准,主要用于规范计算机系统的电源管理和高级配置功能。在服务器领域中,它扮演着关键角色,确保了设备之间的兼容性和高效能的电源管理。"acpi-config-power-interface-spec_3.0a.pdf"文档是该技术的最新版本,发布于2005年12月30日,由Hewlett-Packard(惠普)、Intel Corporation(英特尔)、Microsoft Corporation(微软)、Phoenix Technologies Ltd.(凤凰科技)和Toshiba Corporation(东芝)共同制定。
该标准的主要内容涵盖了以下知识点:
1. **标准化设备电源状态**:ACPI定义了一系列预定义的电源状态(如S0、S1、S3、S4等),用于指示设备在不同能耗水平下的工作状态。这使得操作系统可以更精确地控制硬件的休眠和唤醒,从而节省能源并提高系统的整体效率。
2. **系统级电源管理**:ACPI允许系统管理员通过BIOS设置或软件接口来配置电源管理策略,包括电源计划和电池管理。这有助于在满足性能需求的同时,平衡设备的能耗。
3. **唤醒机制**:文档详细描述了设备如何在接收到特定信号后从低功耗状态(如S3或S4)恢复至S0(运行状态),以及处理器和其他组件的唤醒流程。
4. **兼容性与一致性**:ACPI规范确保各厂商生产的硬件产品能够遵循统一的电源管理协议,从而简化了系统集成和维护过程。
5. **知识产权声明**:文档强调所有参与方保留其知识产权,并规定了该规范提供的无担保性质,即用户和制造商使用此规范时需自行承担风险,不涉及任何默示或明示的保修。
6. **法律责任免责声明**:Hewlett-Packard、Intel、Microsoft、Phoenix和Toshiba对实施本规范可能侵犯的专利或其他知识产权问题不承担任何责任,用户在实施时需要自行评估风险。
ACPI配置电源接口规格3.0a是现代服务器和高性能计算系统设计的核心组成部分,它通过标准化电源管理协议,促进了设备之间的高效协作和电源利用,同时为系统管理员提供了强大的工具来定制和优化系统的性能与节能。对于服务器管理员、硬件工程师以及软件开发者来说,理解和掌握这个标准至关重要。
xvi
Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba
17.5.90 Or (Integer Bitwise Or)........................................................................................................................... 503
17.5.91 Package (Declare Package Object)......................................................................................................... 504
17.5.92 PowerResource (Declare Power Resource) ............................................................................................ 505
17.5.93 Processor (Declare Processor) ................................................................................................................ 505
17.5.94 QWordIO (QWord IO Resource Descriptor Macro)............................................................................... 506
17.5.95 QWordMemory (QWord Memory Resource Descriptor Macro)............................................................ 507
17.5.96 QWordSpace (QWord Space Resource Descriptor Macro).................................................................... 509
17.5.97 RefOf (Create Object Reference) ........................................................................................................... 510
17.5.98 Register (Generic Register Resource Descriptor Macro)........................................................................ 510
17.5.99 Release (Release a Mutex Synchronization Object) ............................................................................... 511
17.5.100 Reset (Reset an Event Synchronization Object) ................................................................................... 511
17.5.101 ResourceTemplate (Resource To Buffer Conversion Macro)............................................................... 512
17.5.102 Return (Return from Method Execution).............................................................................................. 512
17.5.103 Revision (Constant Revision Object).................................................................................................... 512
17.5.104 Scope (Open Named Scope)................................................................................................................. 512
17.5.105 ShiftLeft (Integer Shift Left)................................................................................................................. 513
17.5.106 ShiftRight (Integer Shift Right)............................................................................................................ 513
17.5.107 Signal (Signal a Synchronization Event) .............................................................................................. 513
17.5.108 SizeOf (Get Data Object Size).............................................................................................................. 514
17.5.109 Sleep (Milliseconds Sleep) ................................................................................................................... 514
17.5.110 Stall (Stall for a Short Time) ................................................................................................................ 514
17.5.111 StartDependentFn (Start Dependent Function Resource Descriptor Macro) ........................................ 515
17.5.112 StartDependentFnNoPri (Start Dependent Function Resource Descriptor Macro)............................... 515
17.5.113 Store (Store an Object) ......................................................................................................................... 515
17.5.114 Subtract (Integer Subtract).................................................................................................................... 516
17.5.115 Switch (Select Code To Execute Based On Expression) ...................................................................... 516
17.5.116 ThermalZone (Declare Thermal Zone)................................................................................................. 518
17.5.117 Timer (Get 64-Bit Timer Value)........................................................................................................... 518
17.5.118 ToBCD (Convert Integer to BCD)........................................................................................................ 519
17.5.119 ToBuffer (Convert Data to Buffer)....................................................................................................... 519
17.5.120 ToDecimalString (Convert Data to Decimal String)............................................................................. 519
17.5.121 ToHexString (Convert Data to Hexadecimal String)............................................................................ 520
17.5.122 ToInteger (Convert Data to Integer) ..................................................................................................... 520
17.5.123 ToString (Convert Buffer To String) .................................................................................................... 520
17.5.124 ToUUID (Convert String to UUID Macro) .......................................................................................... 521
17.5.125 Unicode (String To Unicode Conversion Macro)................................................................................. 522
17.5.126 Unload (Unload Definition Block) ....................................................................................................... 522
17.5.127 VendorLong (Long Vendor Resource Descriptor)................................................................................ 522
17.5.128 VendorShort (Short Vendor Resource Descriptor) ............................................................................... 523
17.5.129 Wait (Wait for a Synchronization Event) ............................................................................................. 523
17.5.130 While (Conditional Loop)..................................................................................................................... 523
17.5.131 WordBusNumber (Word Bus Number Resource Descriptor Macro) ................................................... 524
17.5.132 WordIO (Word IO Resource Descriptor Macro) .................................................................................. 525
17.5.133 WordSpace (Word Space Resource Descriptor Macro) ) ..................................................................... 526
17.5.134 XOr (Integer Bitwise Xor).................................................................................................................... 527
17.5.135 Zero (Constant Zero Object)................................................................................................................. 528
18 ACPI MACHINE LANGUAGE (AML) SPECIFICATION........................................................... 529
18.1 Notation Conventions..................................................................................................................................... 529
18.2 AML Grammar Definition ............................................................................................................................ 530
18.2.1 Table and Table Header Encoding............................................................................................................ 530
18.2.2 Name Objects Encoding ........................................................................................................................... 530
18.2.3 Data Objects Encoding ............................................................................................................................. 531
18.2.4 Package Length Encoding ........................................................................................................................ 532
18.2.5 Term Objects Encoding............................................................................................................................ 532
18.2.6 Miscellaneous Objects Encoding.............................................................................................................. 538
18.3 AML Byte Stream Byte Values ..................................................................................................................... 539
xvii
Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba
18.4 AML Encoding of Names in the Namespace................................................................................................ 543
A DEVICE CLASS PM SPECIFICATIONS....................................................................................... 545
A.1 Overview ........................................................................................................................................................ 545
A.2 Device Power States....................................................................................................................................... 545
A.2.1 Bus Power Management.......................................................................................................................... 546
A.2.2 Display Power Management.................................................................................................................... 546
A.2.3 PCMCIA/PCCARD/CardBus Power Management ................................................................................. 546
A.2.4 PCI Power Management.......................................................................................................................... 546
A.2.5 USB Power Management ........................................................................................................................ 546
A.2.6 Device Classes......................................................................................................................................... 547
A.3 Default Device Class...................................................................................................................................... 547
A.3.1 Default Power State Definitions .............................................................................................................. 547
A.3.2 Default Power Management Policy ......................................................................................................... 547
A.3.3 Default Wake Events............................................................................................................................... 548
A.3.4 Minimum Power Capabilities .................................................................................................................. 548
A.4 Audio Device Class........................................................................................................................................ 548
A.4.1 Power State Definitions ........................................................................................................................... 548
A.4.2 Power Management Policy ...................................................................................................................... 548
A.4.3 Wake Events............................................................................................................................................ 549
A.4.4 Minimum Power Capabilities .................................................................................................................. 549
A.5 COM Port Device Class................................................................................................................................ 549
A.5.1 Power State Definitions ........................................................................................................................... 550
A.5.2 Power Management Policy ...................................................................................................................... 550
A.5.3 Wake Events............................................................................................................................................ 550
A.5.4 Minimum Power Capabilities .................................................................................................................. 550
A.6 Display Device Class...................................................................................................................................... 550
A.6.1 Power State Definitions ........................................................................................................................... 551
A.6.2 Power Management Policy for the Display Class.................................................................................... 556
A.6.3 Wake Events............................................................................................................................................ 557
A.6.4 Minimum Power Capabilities .................................................................................................................. 557
A.6.5 Performance States for Display Class Devices ..................................................................................... 557
A.7 Input Device Class......................................................................................................................................... 559
A.7.1 Power State Definitions ........................................................................................................................... 559
A.7.2 Power Management Policy ...................................................................................................................... 559
A.7.3 Wake Events............................................................................................................................................ 560
A.7.4 Minimum Power Capabilities .................................................................................................................. 560
A.8 Modem Device Class ..................................................................................................................................... 560
A.8.1 Technology Overview ............................................................................................................................. 560
A.8.2 Power State Definitions ........................................................................................................................... 561
A.8.3 Power Management Policy ...................................................................................................................... 562
A.8.4 Wake Events............................................................................................................................................ 562
A.8.5 Minimum Power Capabilities .................................................................................................................. 562
A.9 Network Device Class.................................................................................................................................... 563
A.9.1 Power State Definitions ........................................................................................................................... 563
A.9.2 Power Management Policy ...................................................................................................................... 564
A.9.3 Wake Events............................................................................................................................................ 564
A.9.4 Minimum Power Capabilities .................................................................................................................. 564
A.10 PC Card Controller Device Class............................................................................................................... 564
A.10.1 Power State Definitions ......................................................................................................................... 565
A.10.2 Power Management Policy .................................................................................................................... 566
A.10.3 Wake Events.......................................................................................................................................... 566
A.10.4 Minimum Power Capabilities ................................................................................................................ 566
A.11 Storage Device Class ................................................................................................................................... 567
A.11.1 Power State Definitions ......................................................................................................................... 567
A.11.2 Power Management Policy .................................................................................................................... 568
xviii
Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba
A.11.3 Wake Events.......................................................................................................................................... 568
A.11.4 Minimum Power Capabilities ................................................................................................................ 568
B ACPI EXTENSIONS FOR DISPLAY ADAPTERS........................................................................ 569
B.1 Introduction ................................................................................................................................................... 569
B.2 Definitions ...................................................................................................................................................... 570
B.3 ACPI Namespace........................................................................................................................................... 570
B.4 Display-specific Methods............................................................................................................................... 571
B.4.1 _DOS (Enable/Disable Output Switching)............................................................................................... 571
B.4.2 _DOD (Enumerate All Devices Attached to the Display Adapter).......................................................... 572
B.4.3 _ROM (Get ROM Data) .......................................................................................................................... 575
B.4.4 _GPD (Get POST Device) ....................................................................................................................... 576
B.4.5 _SPD (Set POST Device) ........................................................................................................................ 576
B.4.6 _VPO (Video POST Options).................................................................................................................. 577
B.5 Notifications for Display Devices................................................................................................................. 577
B.6 Output Device-specific Methods................................................................................................................... 578
B.6.1 _ADR (Return the Unique ID for this Device) ........................................................................................ 578
B.6.2 _BCL (Query List of Brightness Control Levels Supported)................................................................... 578
B.6.3 _BCM (Set the Brightness Level)............................................................................................................ 579
B.6.4 _BQC (Brightness Query Current level).................................................................................................. 579
B.6.5 _DDC (Return the EDID for this Device)................................................................................................ 579
B.6.6 _DCS (Return the Status of Output Device) ............................................................................................ 580
B.6.7 _DGS (Query Graphics State).................................................................................................................. 580
B.6.8 _DSS – Device Set State.......................................................................................................................... 581
B.7 Notifications Specific to Output Devices...................................................................................................... 582
B.8 Notes on State Changes................................................................................................................................. 582
INDEX....................................................................................................................................................... 585
Introduction 1
Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba
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 evolves the existing 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, new system architectures are being built that stretch the limits of current Plug and Play interfaces.
ACPI evolves the existing motherboard configuration interfaces to support these 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 will reduce 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.
• The OS can evolve independently of the hardware, allowing all ACPI-compatible machines to
gain the benefits of OS improvements and innovations.
2 Advanced Configuration and Power Interface Specification
Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba
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.
Moving power management functionality into the OS makes it available on every
machine on which the OS is installed. The level of functionality (power savings, and so
on) varies from machine to machine, but users and applications will see the same power
interfaces and semantics on all OSPM machines.
This will enable application vendors to invest in adding power management functionality
to their products.
• 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,
and hardware in the OS allows the implementation of more powerful functionality. For
example, an OS can have a policy of dividing I/O operations into normal and lazy. Lazy
I/O operations (such as a word processor saving files in the background) would be
gathered up into clumps and done only when the required I/O device is powered up for
some other reason. A non-lazy I/O request made when the required device was powered
down would cause the device to be powered up immediately, the non-lazy I/O request to
be carried out, and any pending lazy I/O operations to be done. Such a policy requires
knowing when I/O devices are powered up, knowing which application I/O requests are
lazy, and being able to assure that such lazy I/O operations do not starve.
Appliance functions, such as answering machines, require globally coherent power
decisions. For example, a telephone-answering application could call the OS and assert,
“I am waiting for incoming phone calls; any sleep state the system enters must allow me
to wake and answer the telephone in 1 second.” Then, when the user presses the “off”
button, the system would pick the deepest sleep state consistent with the needs of the
phone answering service.
• BIOS code has become very complex to deal with power management. It is difficult to make work
with an OS and is limited to static configurations of the hardware.
There is much less state information for the BIOS to retain and manage (because the OS
manages it).
Power management algorithms are unified in the OS, yielding much better integration
between the OS and the hardware.
Because additional ACPI tables (Definition Blocks) can be loaded, for example, when a
mobile system docks, the OS can deal with dynamic machine configurations.
Because the BIOS has fewer functions and they are simpler, it is much easier (and
therefore cheaper) to implement and support.
• The existing structure of the PC platform constrains OS and hardware designs.
• Because ACPI is abstract, the OS can evolve separately from the hardware and, likewise, the
hardware from the OS.
• ACPI is by nature more portable across operating systems and processors. ACPI control methods
allow for very flexible implementations of particular features.
剩余623页未读,继续阅读
2020-07-03 上传
2022-09-21 上传
2012-04-02 上传
2022-10-22 上传
2021-05-14 上传
2018-04-14 上传
2022-09-20 上传
2021-02-24 上传
2022-09-23 上传
Qazxcv0116
- 粉丝: 68
- 资源: 6
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- Android圆角进度条控件的设计与应用
- mui框架实现带侧边栏的响应式布局
- Android仿知乎横线直线进度条实现教程
- SSM选课系统实现:Spring+SpringMVC+MyBatis源码剖析
- 使用JavaScript开发的流星待办事项应用
- Google Code Jam 2015竞赛回顾与Java编程实践
- Angular 2与NW.js集成:通过Webpack和Gulp构建环境详解
- OneDayTripPlanner:数字化城市旅游活动规划助手
- TinySTM 轻量级原子操作库的详细介绍与安装指南
- 模拟PHP序列化:JavaScript实现序列化与反序列化技术
- ***进销存系统全面功能介绍与开发指南
- 掌握Clojure命名空间的正确重新加载技巧
- 免费获取VMD模态分解Matlab源代码与案例数据
- BuglyEasyToUnity最新更新优化:简化Unity开发者接入流程
- Android学生俱乐部项目任务2解析与实践
- 掌握Elixir语言构建高效分布式网络爬虫
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功