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.

ACPI Software Programming Model<br />

Note: This status code is different than the IPMI completion code, which is returned as the first byte of<br />

the response message in the data buffer payload. The completion code is described in the<br />

complete IPMI specification.<br />

Table 5-138 IPMI Status Codes<br />

Status Code Name Description<br />

00h IPMI OK Indicates the comm<strong>and</strong> has been successfully completed.<br />

07h<br />

IPMI Unknown Indicates failure because of an unknown IPMI error.<br />

Failure<br />

10h<br />

IPMI Comm<strong>and</strong><br />

Operation Timeout<br />

Indicates the operation timed out.<br />

5.5.2.4.4 Declaring GeneralPurposeIO Operation Regions<br />

For GeneralPurposeIO Operation Regions, the syntax for the OperationRegion term (from section<br />

Section 19.6.97, “OperationRegion (Declare Operation Region]”) is described below.<br />

OperationRegion (<br />

RegionName,<br />

RegionSpace,<br />

Offset,<br />

Length<br />

)<br />

Where:<br />

// NameString<br />

// RegionSpaceKeyword<br />

// TermArg=>Integer<br />

// TermArg=>Integer<br />

• RegionName specifies a name for this GeneralPurposeIO region (for example, “GPI1”).<br />

• RegionSpace must be set to GeneralPurposeIO (operation region type value 0x08).<br />

• Offset is ignored for the GeneralPurposeIO RegionSpace.<br />

• Length is the maximum number of GPIO IO pins to be included in the Operation Region,<br />

rounded up to the next byte.<br />

GeneralPurposeIO OpRegions must be declared within the scope of the GPIO controller device<br />

being accessed.<br />

5.5.2.4.4.1 Declaring GeneralPurposeIO Fields<br />

As with other regions, GeneralPurposeIO operation regions are only accessible via the Field term.<br />

Each field element represents a subset of the length bits declared in the OpRegion declaration. The<br />

pins within the OpRegion that are accessed via a given field name are defined by a Connection<br />

descriptor. The total number of defined field bits following a connection descriptor must equal the<br />

number of pins listed in the descriptor.<br />

The syntax for the Field term (from Section 19.6.46) is described below.<br />

Field(<br />

RegionName,<br />

AccessType,<br />

LockRule,<br />

UpdateRule<br />

) {FieldUnitList}<br />

Where:<br />

// NameString=>OperationRegion<br />

// AccessTypeKeyword<br />

// LockRuleKeyword<br />

// UpdateRuleKeyword – ignored<br />

• RegionName specifies the operation region name previously declared.<br />

Version 6.0 227

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

Saved successfully!

Ooh no, something went wrong!