27.10.2015 Views

Advanced Configuration and Power Interface Specification

ACPI_6.0

ACPI_6.0

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

that cannot be changed; however, the bit can be implemented in either register block (A or B). The A<br />

<strong>and</strong> B register blocks for the events allow chipsets to vary the partitioning of events into two or more<br />

chips. For read operations, OSPM will generate a read to the associated A <strong>and</strong> B registers, OR the<br />

two values together, <strong>and</strong> then operate on this result. For write operations, OSPM will write the value<br />

to the associated register in both register blocks. Therefore, there are two rules to follow when<br />

implementing event registers:<br />

• Reserved or unimplemented bits always return zero (control or enable).<br />

• Writes to reserved or unimplemented bits have no affect.<br />

The PM1 CNT grouping contains the fixed hardware feature control bits <strong>and</strong> consists of the<br />

PM1a_CNT_BLK <strong>and</strong> PM1b_CNT_BLK register blocks. Each register block is associated with a<br />

single control register. Each register grouping has a defined bit position that cannot be changed;<br />

however, the bit can be implemented in either register block (A or B). There are two rules to follow<br />

when implementing CNT registers:<br />

• Reserved or unimplemented bits always return zero (control or enable).<br />

• Writes to reserved or unimplemented bits have no affect.<br />

The PM2_CNT_BLK register block currently contains a single bit for the arbiter disable function.<br />

The general-purpose event register contains the event programming model for generic features. All<br />

generic events, just as fixed events, generate SCIs. Generic event status bits can reside anywhere;<br />

however, the top-level generic event resides in one of the general-purpose register blocks. Any<br />

generic feature event status not in the general-purpose register space is considered a child or sibling<br />

status bit, whose parent status bit is in the general-purpose event register space. Notice that it is<br />

possible to have N levels of general-purpose events prior to hitting the GPE event status.<br />

General-purpose event registers are described by two register blocks: The GPE0_BLK or the<br />

GPE1_BLK. Each register block is pointed to separately from within the FADT. Each register block<br />

is further broken into two registers: GPEx_STS <strong>and</strong> GPEx_EN. The status <strong>and</strong> enable registers in the<br />

general-purpose event registers follow the event model for the fixed hardware event registers.<br />

4.8.1 ACPI Register Summary<br />

The following tables summarize the ACPI registers:<br />

Table 4-7<br />

PM1 Event Registers<br />

Register Size (Bytes) Address (relative to register block)<br />

PM1a_STS PM1_EVT_LEN/2 <br />

PM1a_EN PM1_EVT_LEN/2 +PM1_EVT_LEN/2<br />

PM1b_STS PM1_EVT_LEN/2 <br />

PM1b_EN PM1_EVT_LEN/2 +PM1_EVT_LEN/2<br />

Table 4-8<br />

PM1 Control Registers<br />

Register Size (Bytes) Address (relative to register block)<br />

PM1_CNTa PM1_CNT_LEN <br />

PM1_CNTb PM1_CNT_LEN <br />

72 April, 2015 Version 6.0

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

Saved successfully!

Ooh no, something went wrong!