Advanced Configuration and Power Interface Specification

Advanced Configuration and Power Interface Specification
can be found in “Start Dependent Functions Descriptor” (page 345). This macro generates the twobyte
form of the resource descriptor. The macro is designed to be used inside of a ResourceTemplate
(page 882).
19.6.123 StartDependentFnNoPri (Start Dependent Function Resource
Descriptor Macro)
Syntax
StartDependentFnNoPri () {ResourceList}
Description
The StartDependentFnNoPri macro evaluates to a buffer which contains a start dependent function
resource descriptor, which describes a group of resources which must be selected together. Each
subsequent StartDependentFn or StartDependentFnNoPri resource descriptor introduces a new
choice of resources for configuring the device, with the last choice terminated with an
EndDependentFn resource descriptor. The format of the start dependent function resource descriptor
can be found in “Start Dependent Functions Descriptor” (page 345). This macro generates the onebyte
form of the resource descriptor. The macro is designed to be used inside of a ResourceTemplate
(page 882).
This is similar to StartDependentFn (page 887) with both CompatibilityPriority and
PerformancePriority set to 1, but is one byte shorter.
19.6.124 Store (Store an Object)
Syntax
Store (Source, Destination) => DataRefObject
Destination = Source => DataRefObject
Arguments
This operation evaluates Source, converts it to the data type of Destination, and writes the result into
Destination. For information on automatic data-type conversion, see Section 19.3.5, “ASL Data
Types.”
Description
Stores to OperationRegion Field data types may relinquish the processor depending on the region
type.
All stores (of any type) to the constant Zero, constant One, or constant Ones object are not allowed.
Stores to read-only objects are fatal. The execution result of the operation depends on the type of
Destination. For any type other than an operation region field, the execution result is the same as the
data written to Destination. For operation region fields with an AccessType of ByteAcc, WordAcc,
DWordAcc, QWordAcc or AnyAcc, the execution result is the same as the data written to
Destination as in the normal case, but when the AccessType is BufferAcc, the operation region
handler may modify the data when it is written to the Destination so that the execution result
contains modified data.
888 April, 2015 Version 6.0