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.

ACPI Hardware <strong>Specification</strong><br />

ACPI FADT’s GPE0_BLK <strong>and</strong> GPE0_BLK_LEN operators. OSPM owns the general-purpose<br />

event resources <strong>and</strong> these bits are only manipulated by OSPM; AML code cannot access the generalpurpose<br />

event registers.<br />

It is envisioned that chipsets will contain GPE event registers that provide GPE input pins for<br />

various events.<br />

The platform designer would then wire the GPEs to the various value-added event hardware <strong>and</strong> the<br />

AML code would describe to OSPM how to utilize these events. As such, there will be the case<br />

where a platform has GPE events that are not wired to anything (they are present in the chip set), but<br />

are not utilized by the platform <strong>and</strong> have no associated AML code. In such, cases these event pins<br />

are to be tied inactive such that the corresponding SCI status bit in the GPE register is not set by a<br />

floating input pin.<br />

4.8.4.1.1.1 General-Purpose Event 0 Status Register<br />

Register Location: System I/O or System Memory Space<br />

Default Value:<br />

00h<br />

Attribute:<br />

Read/Write<br />

Size:<br />

GPE0_BLK_LEN/2<br />

The general-purpose event 0 status register contains the general-purpose event status bits in bank<br />

zero of the general-purpose registers. Each available status bit in this register corresponds to the bit<br />

with the same bit position in the GPE0_EN register. Each available status bit in this register is set<br />

when the event is active, <strong>and</strong> can only be cleared by software writing a “1” to its respective bit<br />

position. For the general-purpose event registers, unimplemented bits are ignored by OSPM.<br />

Each status bit can optionally wake the system if asserted when the system is in a sleeping state with<br />

its respective enable bit set. OSPM accesses GPE registers through byte accesses (regardless of their<br />

length).<br />

4.8.4.1.1.2 General-Purpose Event 0 Enable Register<br />

Register Location: System I/O or System Memory Space<br />

Default Value:<br />

00h<br />

Attribute:<br />

Read/Write<br />

Size:<br />

GPE0_BLK_LEN/2<br />

The general-purpose event 0 enable register contains the general-purpose event enable bits. Each<br />

available enable bit in this register corresponds to the bit with the same bit position in the<br />

GPE0_STS register. The enable bits work similarly to how the enable bits in the fixed-event<br />

registers are defined: When the enable bit is set, then a set status bit in the corresponding status bit<br />

will generate an SCI bit. OSPM accesses GPE registers through byte accesses (regardless of their<br />

length).<br />

4.8.4.1.2 General-Purpose Event 1 Register Block<br />

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

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

ACPI FADT’s GPE1_BLK <strong>and</strong> GPE1_BLK_LEN operators.<br />

Version 6.0 97

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

Saved successfully!

Ooh no, something went wrong!