ACPI_EVAL_INPUT_BUFFER_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_V1_EX {
  ULONG Signature;
  CHAR  MethodName[256];
} ACPI_EVAL_INPUT_BUFFER_V1_EX, *PACPI_EVAL_INPUT_BUFFER_V1_EX, ACPI_EVAL_INPUT_BUFFER_EX, *PACPI_EVAL_INPUT_BUFFER_EX;
View the official Windows Driver Kit DDI reference

NtDoc

No description available.

Windows Driver Kit DDI reference (ns-acpiioct-_acpi_eval_input_buffer_v1_ex)

_ACPI_EVAL_INPUT_BUFFER_V1_EX structure

Description

The ACPI_EVAL_INPUT_BUFFER_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 that does not take an input argument.

Members

Signature

The signature of an input buffer that does not include an argument, which must be set to ACPI_EVAL_INPUT_BUFFER_SIGNATURE_EX.

MethodName

A 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.

Remarks

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 does not take input arguments, these requests take an input ACPI_EVAL_INPUT_BUFFER_EX structure as follows:

For more information about how to use this structure, see Evaluating ACPI Control Methods.

See also

IOCTL_ACPI_ASYNC_EVAL_METHOD_EX

IOCTL_ACPI_EVAL_METHOD_EX