27.10.2015 Views

Advanced Configuration and Power Interface Specification

ACPI_6.0

ACPI_6.0

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Advanced</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Power</strong> <strong>Interface</strong> <strong>Specification</strong><br />

For each of the status bits in the GPEx_STS register, there is a corresponding enable bit in the<br />

GPEx_EN register. Notice that the child status bits do not necessarily need enable bits (see the<br />

DOCK_STS bit).<br />

The lid logic contains a control bit to determine if its status bit is set when the LID is open<br />

(LID_POL is set <strong>and</strong> LID is set) or closed (LID_POL is clear <strong>and</strong> LID is clear). This control bit<br />

resides in generic I/O space (in this case, bit 2 of system I/O space 33h) <strong>and</strong> would be manipulated<br />

with a control method associated with the lid object.<br />

As with fixed hardware events, OSPM will clear the status bits in the GPEx register blocks.<br />

However, AML code clears all sibling status bits in the generic hardware.<br />

Generic hardware features are controlled by OEM supplied control methods, encoded in AML.<br />

ACPI provides both an event <strong>and</strong> control model for development of these features. The ACPI<br />

specification also provides specific control methods for notifying OSPM of certain power<br />

management <strong>and</strong> Plug <strong>and</strong> Play events. Section 5, “ACPI Software Programming Model,” provides<br />

information on the types of hardware functionality that support the different types of subsystems.<br />

The following is a list of features supported by ACPI. The list is not intended to be complete or<br />

comprehensive.<br />

• Device insertion/ejection (for example, docking, device bay, A/C adapter)<br />

• Batteries 1<br />

• Platform thermal subsystem<br />

• Turning on/off power resources<br />

• Mobile lid <strong>Interface</strong><br />

• Embedded controller<br />

• System indicators<br />

• OEM-specific wake events<br />

• Plug <strong>and</strong> Play configuration<br />

4.8.4.1 General-Purpose Event Register Blocks<br />

ACPI supports up to two general-purpose register blocks as described in the FADT (see Section 5,<br />

“ACPI Software Programming Model”) <strong>and</strong> an arbitrary number of additional GPE blocks described<br />

as devices within the ACPI namespace. Each register block contains two registers: an enable <strong>and</strong> a<br />

status register. Each register block is 32-bit aligned. Each register in the block is accessed as a byte.<br />

It is up to the specific design to determine if these bits retain their context across sleeping or soft-off<br />

states. If they lose their context across a sleeping or soft-off state, then BIOS resets the respective<br />

enable bit prior to passing control to the OS upon waking.<br />

4.8.4.1.1 General-Purpose Event 0 Register Block<br />

This register block consists of two registers: The GPE0_STS <strong>and</strong> the GPE0_EN registers. Each<br />

register’s length is defined to be half the length of the GPE0 register block, <strong>and</strong> is described in the<br />

1. ACPI operating systems assume the use of the Smart Battery System Implementers Forum defined st<strong>and</strong>ard<br />

for batteries, called the “Smart Battery <strong>Specification</strong>” (SBS). ACPI provides a set of control methods for use by<br />

OEMs that use a proprietary “control method” battery interface.<br />

96 April, 2015 Version 6.0

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!