ACPI_EVAL_INPUT_BUFFER_COMPLEX_V1_EX - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// acpiioct.h
typedef struct _ACPI_EVAL_INPUT_BUFFER_COMPLEX_V1_EX {
ULONG Signature;
CHAR MethodName[256];
ULONG Size;
ULONG ArgumentCount;
ACPI_METHOD_ARGUMENT_V1 Argument[ANYSIZE_ARRAY];
} ACPI_EVAL_INPUT_BUFFER_COMPLEX_V1_EX, *PACPI_EVAL_INPUT_BUFFER_COMPLEX_V1_EX, ACPI_EVAL_INPUT_BUFFER_COMPLEX_EX, *PACPI_EVAL_INPUT_BUFFER_COMPLEX_EX;
View the official Windows Driver Kit DDI referenceNo description available.
The ACPI_EVAL_INPUT_BUFFER_COMPLEX_EX structure is used as input to an IOCTL_ACPI_EVAL_METHOD_EX request and to an IOCTL_ACPI_ASYNC_EVAL_METHOD_EX request. The structure supplies the path and name of a control method in an ACPI namespace and an input argument array of ACPI_METHOD_ARGUMENT structures.
SignatureThe signature of an extended complex input buffer, which must be set to ACPI_EVAL_INPUT_BUFFER_COMPLEX_SIGNATURE_EX.
MethodNameA NULL-terminated ASCII string that contains the path and name of a control method in an ACPI namespace. The maximum number of characters that the string can contain, including a NULL terminator, is 256.
For more information about how to supply the path and name of a control method, see the Remarks section later in this topic.
SizeThe number of bytes that the Argument array contains.
ArgumentCountThe number of variable-length ACPI_METHOD_ARGUMENT structures that the Argument array contains. The Argument array can hold a maximum of seven argument structures.
ArgumentAn array of ACPI_METHOD_ARGUMENT structures.
A driver for a device can use an IOCTL_ACPI_EVAL_METHOD_EX request or an IOCTL_ACPI_ASYNC_EVAL_METHOD_EX request to evaluate a control method that is a descendant child object of the device. If the method takes a complex array of arguments, these requests take an input ACPI_EVAL_INPUT_BUFFER_COMPLEX_EX structure as follows:
Set MethodName to a NULL-terminated string that supplies either the full path and name to a control method in the ACPI namespace or the path and name of the method relative to the device to which the evaluation request is sent.
For example, assume that a request is sent to a device named 'ABCD,' which is an immediate child of the root of an ACPI namespace, that 'ABCD' device supports a child device named 'CHLD,' and that the 'CHLD' device supports a method named '_FOO.' In this case, the evaluation request can supply either '\ABCD.CHLD._FOO,' which is the fully qualified path and name of the control method in the ACPI namespace, or 'CHLD._FOO,' which is the path and name of the control method that is relative to the 'ABCD' device in the ACPI namespace.
For more information about how to obtain the fully qualified path and name of a control method in an ACPI namespace, see Enumerating Child Devices and Control Methods.
For more information about how to use this structure, see Evaluating ACPI Control Methods.
IOCTL_ACPI_ASYNC_EVAL_METHOD_EX