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 Software Programming Model<br />

• UpdateRule is not applicable to GenericSerialBus operation regions since each virtual register is<br />

accessed in its entirety. This field is ignored for all GenericSerialBus field definitions.<br />

GenericSerialBus operation regions require that all field elements be declared at comm<strong>and</strong> value<br />

granularity. This means that each virtual register cannot be broken down to its individual bits within<br />

the field definition.<br />

Access to sub-portions of virtual registers can be done only outside of the field definition. This<br />

limitation is imposed to simplify the GenericSerialBus interface.<br />

GenericSerialBus protocols are assigned to field elements using the AccessAs term within the field<br />

definition. The syntax for this term (from Section 19.2.3, “ASL Root <strong>and</strong> SecondaryTerms”) is<br />

described below.<br />

AccessAs(<br />

AccessType,<br />

AccessAttribute<br />

)<br />

Where:<br />

//AccessTypeKeyword<br />

//Nothing | ByteConst | AccessAttribKeyword<br />

• AccessType must be set to BufferAcc.<br />

• AccessAttribute indicates the GenericSerialBus protocol to assign to comm<strong>and</strong> values that<br />

follow this term. SeeSection 5.5.2.4.5.3, “Using the GenericSerialBus Protocols,” for a listing of<br />

the GenericSerialBus protocols.<br />

An AccessAs term must appear in a field definition to set the initial GenericSerialBus protocol for<br />

the field elements that follow. A maximum of one GenericSerialBus protocol may be defined for<br />

each field element. Devices supporting multiple protocols for a single comm<strong>and</strong> value can be<br />

modeled by specifying multiple field elements with the same offset (comm<strong>and</strong> value), where each<br />

field element is preceded by an AccessAs term specifying an alternate protocol.<br />

For GenericSerialBus operation regions, connection attributes must be defined for each set of field<br />

elements. GenericSerialBus resources are assigned to field elements using the Connection term<br />

within the field definition. The syntax for this term (from Section 19.6.15 “Connection (Declare<br />

Field Connection Attributes)”) is described below.<br />

Connection (ConnectionResourceObj)<br />

Where:<br />

• ConnectionResourceObj points to a Serial Bus Resource Connection Descriptor (see<br />

Section 6.4.3.8.2, “Serial Bus Connection Resource Descriptors” for valid types), or a named<br />

object that specifies a buffer field containing the connection resource information.<br />

Each Field definition references the initial comm<strong>and</strong> offset specified in the operation region<br />

definition. The offset is iterated for each subsequent field element defined in that respective Field. If<br />

a new connection is described in the same Field definition, the offset will not be returned to its initial<br />

value <strong>and</strong> a new Field must be defined to inherit the initial comm<strong>and</strong> value offset from the operation<br />

region definition. The following example illustrates this point.<br />

Version 6.0 231

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

Saved successfully!

Ooh no, something went wrong!