Advanced Configuration and Power Interface Specification

More documents

Recommendations

Info

Introduction 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. • 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. • 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 2 Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba
Advanced Configuration and Power Interface Specification 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. 1.3 Legacy Support ACPI provides support for an orderly transition from legacy hardware to ACPI hardware, and allows for both mechanisms to exist in a single machine and be used as needed. Table 1-1 Hardware Type vs. OS Type Interaction Hardware\OS Legacy OS ACPI OS with OSPM Legacy hardware A legacy OS on legacy hardware does what it always did. Legacy and ACPI hardware support in machine It works just like a legacy OS on legacy hardware. 1.4 OEM Implementation Strategy If the OS lacks legacy support, legacy support is completely contained within the hardware functions. During boot, the OS tells the hardware to switch from legacy to OSPM/ACPI mode and from then on, the system has full OSPM/ACPI support. ACPI-only hardware There is no power management. There is full OSPM/ACPI support. Any OEM is, as always, free to build hardware as they see fit. Given the existence of the ACPI specification, two general implementation strategies are possible: • An original equipment manufacturer (OEM) can adopt the OS vendor-provided ACPI OSPM software and implement the hardware part of the ACPI specification (for a given platform) in one of many possible ways. Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba 3
Page 1 and 2: Advanced Configuration and Power In
Page 3 and 4: Revision History Revision Change De
Page 5 and 6: Revision Change Description Affecte
Page 7 and 8: Revision Change Description Affecte
Page 9 and 10: 1 � 2 � 3 � Advanced Configur
Page 13 and 14: 7 � Advanced Configuration and Po
Page 37: Advanced Configuration and Power In
Page 41 and 42: Device Driver Existing industry sta
Page 49 and 50: 1.9.2 Programming Models Advanced C
Page 51 and 52: 1.10 Related Documents Advanced Con
Page 57 and 58: I/O SAPIC Advanced Configuration an
Page 77 and 78: PWR1_EN PWR2_EN MDM_D3 MDM_D1 COM_D
Page 89 and 90:
Advanced Configuration and Power In
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Legacy Legacy Boot (SCI_EN=0) Legac
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
4.8.1.2 PM1 Control Registers Advan
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
4.8.2.4 Real Time Clock Alarm Advan
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Field Byte Length Advanced Configur
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
FACP - Flag Bit Length Advanced Con
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Field X Firmware Waking Vector Adva
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Field Byte Length Parking Protocol
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
5.2.16.2 Memory Affinity Structure
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
5.2.20.5.1 Sequence of Operations:
Page 201 and 202:
Table 5-81 MPST Table Structure 5.2
Page 203 and 204:
MEMORY_POWER _STATUS_REGIST ER Adva
Page 205 and 206:
Page 207 and 208:
Table 5-87 Flag format Advanced Con
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Table 5-93 Socket Structure Advance
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Root R \_PR P \PID0 \_SB d CPU0 _ST
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Hex value Description Advanced Conf
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Arguments: (1) Advanced Configurati
Page 283 and 284:
Page 285 and 286:
5.7.5 _DLM (DeviceLock Mutex) Advan
Page 287 and 288:
Return Value: None Advanced Configu
Page 289 and 290:
Page 291 and 292:
6.1.2 _CID (Compatible ID) Advanced
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Device(BUS0) { } Advanced Configura
Page 309 and 310:
Page 311 and 312:
Example: Advanced Configuration and
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
6.2.10.1 Rules for Evaluating _OSC
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Scope(\_SB.PCI0) { Advanced Configu
Page 339 and 340:
Return Value: None Argument Informa
Page 341 and 342:
Status Code Description 0xA0-0xFFFF
Page 343 and 344:
Page 345 and 346:
Arguments: None Return Value: Advan
Page 347 and 348:
Offset Field Name Advanced Configur
Page 349 and 350:
Page 351 and 352:
6.4.2.7 Fixed DMA Descriptor Advanc
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Byte 3 Interrupt Vector Flags Advan
Page 373 and 374:
Byte 11 Byte 12 Byte 13 Byte 14 Adv
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
6.5.7 _GLK (Global Lock) Advanced C
Page 393 and 394:
Page 395 and 396:
7.1.3 _ON Advanced Configuration an
Page 397 and 398:
Object Description Advanced Configu
Page 399 and 400:
Arguments: None Return Value: None
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
7.2.17 _S2D (S2 Device State) Advan
Page 407 and 408:
Page 409 and 410:
7.3.1 \_BFS (Back From Sleep) Advan
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
8.4 Declaring Processors Advanced C
Page 431 and 432:
} Advanced Configuration and Power
Page 433 and 434:
Example Advanced Configuration and
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
8.4.3.5 _TDL (T-state Depth Limit)
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Page 453 and 454:
Element Object Type Counter Wraparo
Page 455 and 456:
8.4.5.1.1.3 Lowest Nonlinear Perfor
Page 457 and 458:
8.4.5.1.2.1 Maximum Performance Reg
Page 459 and 460:
Page 461 and 462:
Page 463 and 464:
} }) Advanced Configuration and Pow
Page 465 and 466:
8.5.2 OSPM _OST Evaluation Advanced
Page 467 and 468:
Page 469 and 470:
9.2.1 Overview Advanced Configurati
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Return Value: Advanced Configuratio
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
} } } }) Advanced Configuration and
Page 495 and 496:
Page 497 and 498:
9.12.4 Example: Memory Device Scope
Page 499 and 500:
Page 501 and 502:
Page 503 and 504:
Page 505 and 506:
Page 507 and 508:
Page 509 and 510:
Page 511 and 512:
Page 513 and 514:
Page 515 and 516:
Arguments: (0) Return Value: Advanc
Page 517 and 518:
Page 519 and 520:
Page 521 and 522:
Page 523 and 524:
Page 525 and 526:
Page 527 and 528:
Host Interface Advanced Configurati
Page 529 and 530:
Page 531 and 532:
Page 533 and 534:
10.2.1 Battery Events Advanced Conf
Page 535 and 536:
Page 537 and 538:
Page 539 and 540:
Page 541 and 542:
Page 543 and 544:
10.2.2.9 _BCT (Battery Charge Time)
Page 545 and 546:
Page 547 and 548:
1 - On-line Advanced Configuration
Page 549 and 550:
Object Description Advanced Configu
Page 551 and 552:
Page 553 and 554:
Page 555 and 556:
Page 557 and 558:
Page 559 and 560:
Page 561 and 562:
11.1.5 Passive Cooling Advanced Con
Page 563 and 564:
11.2 Cooling Preferences Advanced C
Page 565 and 566:
Page 567 and 568:
Page 569 and 570:
Page 571 and 572:
Page 573 and 574:
Page 575 and 576:
Page 577 and 578:
Page 579 and 580:
Page 581 and 582:
Page 583 and 584:
Page 585 and 586:
Page 587 and 588:
} Advanced Configuration and Power
Page 589 and 590:
Page 591 and 592:
External(\_SB.CPU1, DeviceObj) Adva
Page 593 and 594:
Page 595 and 596:
Page 597 and 598:
Page 599 and 600:
Page 601 and 602:
Page 603 and 604:
Page 605 and 606:
Page 607 and 608:
Status Code All other error codes a
Page 609 and 610:
Where: Advanced Configuration and P
Page 611 and 612:
Data Returned: 12.9.2.3 Send Byte D
Page 613 and 614:
Data Returned: 12.9.2.9 Write Block
Page 615 and 616:
12.10 SMBus Devices Advanced Config
Page 617 and 618:
Page 619 and 620:
Page 621 and 622:
Page 623 and 624:
13.1.3 SMBus Status Codes Advanced
Page 625 and 626:
OperationRegion (� RegionName, //
Page 627 and 628:
Page 629 and 630:
Page 631 and 632:
Page 633 and 634:
Page 635 and 636:
Page 637 and 638:
Page 639 and 640:
Page 641 and 642:
Page 643 and 644:
Page 645 and 646:
Page 647 and 648:
Page 649 and 650:
Page 651 and 652:
16.1 Sleeping States Advanced Confi
Page 653 and 654:
Page 655 and 656:
Page 657 and 658:
Page 659 and 660:
Page 661 and 662:
Page 663 and 664:
Page 665 and 666:
Page 667 and 668:
Page 669 and 670:
Page 671 and 672:
Page 673 and 674:
Page 675 and 676:
Page 677 and 678:
Page 679 and 680:
Page 681 and 682:
Field Byte Length Max Sections Per
Page 683 and 684:
Page 685 and 686:
Page 687 and 688:
Page 689 and 690:
18.5.1.1 Serialization Actions Adva
Page 691 and 692:
Page 693 and 694:
Page 695 and 696:
Page 697 and 698:
Page 699 and 700:
Field Byte length Advanced Configur
Page 701 and 702:
Page 703 and 704:
Page 705 and 706:
Page 707 and 708:
Page 709 and 710:
Page 711 and 712:
Page 713 and 714:
Page 715 and 716:
Result // Target� ) => Integer Ad
Page 717 and 718:
) DebugTerm :=� Debug Advanced Co
Page 719 and 720:
) Advanced Configuration and Power
Page 721 and 722:
Result // Target� ) => Advanced
Page 723 and 724:
Page 725 and 726:
Page 727 and 728:
Transfer8 | Transfer16 | Transfer8_
Page 729 and 730:
Page 731 and 732:
Page 733 and 734:
Page 735 and 736:
Page 737 and 738:
Page 739 and 740:
19.2.4 ASL Macros Advanced Configur
Page 741 and 742:
EISAID FromBCD ToBCD Advanced Confi
Page 743 and 744:
Page 745 and 746:
Page 747 and 748:
To convert from an object of this D
Page 749 and 750:
Page 751 and 752:
Page 753 and 754:
Page 755 and 756:
Page 757 and 758:
Break BreakPoint Case Continue Defa
Page 759 and 760:
Page 761 and 762:
Page 763 and 764:
Page 765 and 766:
Page 767 and 768:
Page 769 and 770:
Arguments Advanced Configuration an
Page 771 and 772:
Page 773 and 774:
Page 775 and 776:
Page 777 and 778:
Page 779 and 780:
Page 781 and 782:
Page 783 and 784:
Page 785 and 786:
Page 787 and 788:
Page 789 and 790:
Page 791 and 792:
Page 793 and 794:
Page 795 and 796:
Page 797 and 798:
Arguments Addend is evaluated as an
Page 799 and 800:
Store (“ABCDEFGH”, Index (BUFF,
Page 801 and 802:
Page 803 and 804:
Page 805 and 806:
Page 807 and 808:
Page 809 and 810:
Page 811 and 812:
Page 813 and 814:
Page 815 and 816:
Page 817 and 818:
Page 819 and 820:
Page 821 and 822:
Page 823 and 824:
Page 825 and 826:
Page 827 and 828:
Page 829 and 830:
Page 831 and 832:
Page 833 and 834:
Page 835 and 836:
Page 837 and 838:
Name (CNT, 5) Store (CNT, Local0) A
Page 839 and 840:
Page 841 and 842:
Page 843 and 844:
Note: (Compatibility Note) New for
Page 845 and 846:
Page 847 and 848:
Page 849 and 850:
Page 851 and 852:
Page 853 and 854:
Page 855 and 856:
Page 857 and 858:
Page 859 and 860:
Page 861 and 862:
DefSleep := SleepOp MsecTime SleepO
Page 863 and 864:
Page 865 and 866:
20.2.6.2 Local Objects Encoding Adv
Page 867 and 868:
Encoding Value Advanced Configurati
Page 869 and 870:
Encoding Value Advanced Configurati
Page 871 and 872:
\ S0 S1 MEM MEM CPU SET GET SET GET
Page 873 and 874:
Page 875 and 876:
Page 877 and 878:
Page 879 and 880:
21.2.3.4 Strings Advanced Configura
Page 881 and 882:
Page 883 and 884:
Page 885 and 886:
Page 887 and 888:
Page 889 and 890:
Page 891 and 892:
A.4.1 Power State Definitions Advan
Page 893 and 894:
A.5.1 Power State Definitions Advan
Page 895 and 896:
Page 897 and 898:
Page 899 and 900:
Page 901 and 902:
Page 903 and 904:
Page 905 and 906:
State Status Definition Advanced Co
Page 907 and 908:
Page 909 and 910:
Page 911 and 912:
Page 913 and 914:
Page 915 and 916:
Page 917 and 918:
Page 919 and 920:
Primary Desktop Secondary Desktop T
Page 921 and 922:
Page 923 and 924:
Page 925 and 926:
Page 927 and 928:
Page 929 and 930:
Page 931 and 932:
Symbols _EJx 301 A AC adapter devic
Page 933 and 934:
primary terms 678 reserved object n
Page 935 and 936:
Case (Conditional Execution) 728 ca
Page 937 and 938:
D1 Device State definition 27 trans
Page 939 and 940:
EFI definition 19 GetMemoryMap inte
Page 941 and 942:
definition 20 events 20 registers 2
Page 943 and 944:
hung systems 75, 76 hysteresis 522
Page 945 and 946:
LNotEqual (Logical Not Equal) 769 L
Page 947 and 948:
Notification Temperature Threshold
Page 949 and 950:
implementation requirements 10 pass
Page 951 and 952:
performance states 43 performance v
Page 953 and 954:
estoring system context 619 results
Page 955 and 956:
commands, restricted 580 data buffe
Page 957 and 958:
throttling 387, 400 THT_EN 90 Timer
show all

Advanced Configuration and Power Interface Specification

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?