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 />

In theory, it might be possible to define something like PCI configuration space in a Definition<br />

Block by building it from I/O space, but that is not the goal of the definition block. Such a space is<br />

usually defined as a “built in” operator.<br />

Some AML operators perform simple functions, <strong>and</strong> others encompass complex functions. The<br />

power of the Definition block comes from its ability to allow these operations to be glued together in<br />

numerous ways, to provide functionality to OSPM.<br />

The AML operators defined in this specification are intended to allow many useful hardware designs<br />

to be easily expressed, not to allow all hardware designs to be expressed.<br />

Note: To accommodate addressing beyond 32 bits, the integer type was exp<strong>and</strong>ed to 64 bits in ACPI<br />

2.0, see Section 19.3.5, “ASL Data Types”. Existing ACPI definition block implementations may<br />

contain an inherent assumption of a 32-bit integer width. Therefore, to maintain backwards<br />

compatibility, OSPM uses the Revision field, in the header portion of system description tables<br />

containing Definition Blocks, to determine whether integers declared within the Definition Block<br />

are to be evaluated as 32-bit or 64-bit values. A Revision field value greater than or equal to 2<br />

signifies that integers declared within the Definition Block are to be evaluated as 64-bit values. The<br />

ASL writer specifies the value for the Definition Block table header’s Revision field via the ASL<br />

Definition Block’s ComplianceRevision field. See Section 19.6.28, “DefinitionBlock (Declare<br />

Definition Block)”, for more information. It is the responsibility of the ASL writer to ensure the<br />

Definition Block’s compatibility with the corresponding integer width when setting the<br />

ComplianceRevision field.<br />

5.2.11.1 Differentiated System Description Table (DSDT)<br />

The Differentiated System Description Table (DSDT) is part of the system fixed description. The<br />

DSDT is comprised of a system description table header followed by data in Definition Block<br />

format. This Definition Block is like all other Definition Blocks, with the exception that it cannot be<br />

unloaded. See Section 5.2.11, “Definition Blocks,” for a description of Definition Blocks. During<br />

initialization, OSPM finds the pointer to the DSDT in the Fixed ACPI Description Table (using the<br />

FADT’s DSDT or X_DSDT fields) <strong>and</strong> then loads the DSDT to create the ACPI Namespace.<br />

Table 5-42 Differentiated System Description Table Fields (DSDT)<br />

Field<br />

Byte<br />

Length<br />

Byte<br />

Offset<br />

Description<br />

Header<br />

Signature 4 0 ‘DSDT’ Signature for the Differentiated System Description<br />

Table.<br />

Length 4 4 Length, in bytes, of the entire DSDT (including the header).<br />

Revision 1 8 2. This field also sets the global integer width for the AML<br />

interpreter. Values less than two will cause the interpreter to use<br />

32-bit integers <strong>and</strong> math. Values of two <strong>and</strong> greater will cause the<br />

interpreter to use full 64-bit integers <strong>and</strong> math.<br />

Checksum 1 9 Entire table must sum to zero.<br />

OEMID 6 10 OEM ID<br />

OEM Table ID 8 16 The manufacture model ID.<br />

OEM Revision 4 24 OEM revision of DSDT for supplied OEM Table ID.<br />

136 April, 2015 Version 6.0

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

Saved successfully!

Ooh no, something went wrong!