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

FindSetRightBitTerm | FprintfTerm | FromBCDTerm | IncTerm | IndexTerm | LAndTerm |<br />

LEqualTerm | LGreaterTerm | LGreaterEqualTerm | LLessTerm | LLessEqualTerm | LNotTerm |<br />

LNotEqualTerm | LoadTableTerm | LOrTerm | MatchTerm | MidTerm |ModTerm | MultiplyTerm |<br />

NAndTerm | NOrTerm | NotTerm | ObjectTypeTerm | OrTerm | PrintfTerm |RefOfTerm |<br />

ShiftLeftTerm | ShiftRightTerm | SizeOfTerm | StoreTerm | SubtractTerm | TimerTerm |<br />

ToBCDTerm | ToBufferTerm | ToDecimalStringTerm | ToHexStringTerm | ToIntegerTerm |<br />

ToStringTerm | WaitTerm | XorTerm | MethodInvocationTerm | SymbolicExpressionTerm |<br />

SymbolicAssignmentTerm<br />

A Type 2 opcode returns a value <strong>and</strong> can be used in an expression.<br />

Type3Opcode :=<br />

AddTerm | AndTerm | DecTerm | DerefOfTerm | DivideTerm | EISAIDTerm |<br />

FindSetLeftBitTerm | FindSetRightBitTerm | FromBCDTerm | IncTerm | LAndTerm |<br />

LEqualTerm | LGreaterTerm | LGreaterEqualTerm | LLessTerm | LLessEqualTerm | LNotTerm |<br />

LNotEqualTerm | LOrTerm | MatchTerm | ModTerm | MultiplyTerm | NAndTerm | NOrTerm |<br />

NotTerm | OrTerm | ShiftLeftTerm | ShiftRightTerm | SubtractTerm | ToBCDTerm |<br />

ToIntegerTerm | XorTerm | SymbolicExpressionTerm<br />

The Type 3 opcodes are a subset of Type 2 opcodes that return an Integer value <strong>and</strong> can be used in<br />

an expression that evaluates to a constant. These opcodes may be evaluated at ASL compile-time. To<br />

ensure that these opcodes will evaluate to a constant, the following rules apply: The term cannot<br />

have a destination (target) oper<strong>and</strong>, <strong>and</strong> must have either a Type3Opcode, Type4Opcode, Type5Opcode,<br />

ConstExprTerm, Integer, BufferTerm, Package, or String for all arguments.<br />

Type4Opcode :=<br />

ConcatTerm | DerefOfTerm | FprintfTerm | MidTerm | PrintfTerm | ToDecimalStringTerm |<br />

ToHexStringTerm | ToStringTerm<br />

The Type 4 opcodes are a subset of Type 2 opcodes that return a String value <strong>and</strong> can be used in an<br />

expression that evaluates to a constant. These opcodes may be evaluated at ASL compile-time. To<br />

ensure that these opcodes will evaluate to a constant, the following rules apply: The term cannot<br />

have a destination (target) oper<strong>and</strong>, <strong>and</strong> must have either a Type3Opcode, Type4Opcode, Type5Opcode,<br />

ConstExprTerm, Integer, BufferTerm, Package, or String for all arguments.<br />

Type5Opcode :=<br />

ConcatTerm | ConcatResTerm | DerefOfTerm | MidTerm | ResourceTemplateTerm |<br />

ToBufferTerm | ToPLDTerm | ToUUIDTerm | UnicodeTerm<br />

The Type 5 opcodes are a subset of Type 2 opcodes that return a Buffer value <strong>and</strong> can be used in an<br />

expression that evaluates to a constant. These opcodes may be evaluated at ASL compile-time. To<br />

ensure that these opcodes will evaluate to a constant, the following rules apply: The term cannot<br />

760 April, 2015 Version 6.0

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

Saved successfully!

Ooh no, something went wrong!