IOCTL_ACPI_ASYNC_EVAL_METHOD control code

A driver for a device can use the IOCTL_ACPI_ASYNC_EVAL_METHOD device control request to asynchronously evaluate an ACPI control method that is supported by the device. The driver should call IoBuildDeviceIoControlRequest and pass the following input and output parameters to build this request.

Input Parameters

Set the IoBuildDeviceIoControlRequest input parameters as follows:

  • IoControlCode is set to IOCTL_ACPI_ASYNC_EVAL_METHOD.

  • DeviceObject is set to a pointer to the physical device object (PDO) of the device.

  • InputBuffer is set to a pointer to an input buffer structure that depends on the type of input arguments to be passed to the control method. For more information about the type of input arguments that this IOCTL supports, see the Remarks section later in this topic.

  • InputBufferLength is set to the size, in bytes, of the input buffer that is supplied by InputBuffer.

  • OutputBufferLength supplies the size, in bytes, of the output buffer that is supplied by OutputBuffer.

  • InternalDeviceIoControl is set to FALSE.

  • Event is set to NULL.

Output Parameters

Set the IoBuildDeviceIoControlRequest output parameters as follows:

I/O Status Block

If the request succeeds, IoStatusBlock->Status is set to STATUS_SUCCESS; otherwise, the Status member is set to an error code. If the output buffer is not large enough to contain the output buffer header, the Status member is set to STATUS_BUFFER_TOO_SMALL. If the output buffer is large enough to contain the output buffer header, but is not large enough to contain all the output arguments from the control method, the Status member is set to STATUS_BUFFER_OVERFLOW, and OutputBuffer->Length is set to the required length of the output buffer.

If the request succeeds, the IoStatusBlock->Information member is set to the number of bytes that is returned in the output buffer; otherwise, the Information member is set to zero.

Remarks

A driver for a device can use IOCTL_ACPI_ASYNC_EVAL_METHOD to asynchronously evaluate a control method that the device supports. For example, if the device is named 'ABCD' in an ACPI namespace and the 'ABCD' device supports a method named '_FOO,' this IOCTL can be used to evaluate control method '_FOO' by sending the request to the 'ABCD' device and supplying the control method name '_FOO.'

IOCTL_ACPI_ASYNC_EVAL_METHOD supports the following types of input buffer structures:

ACPI_EVAL_INPUT_BUFFER

ACPI_EVAL_INPUT_BUFFER_SIMPLE_INTEGER

ACPI_EVAL_INPUT_BUFFER_SIMPLE_STRING

ACPI_EVAL_INPUT_BUFFER_COMPLEX

The output arguments from the control method are returned in the variable-length ACPI_EVAL_OUTPUT_BUFFER structure that is supplied by the OutBuffer pointer. The ACPI_EVAL_OUTPUT_BUFFER includes an array of variable-length ACPI_METHOD_ARGUMENT structures, each of which returns an output argument.

For information about how to evaluate ACPI control methods synchronously, see IOCTL_ACPI_EVAL_METHOD, IOCTL_ACPI_EVAL_METHOD_EX, and Evaluating ACPI Control Methods Synchronously.

IOCTL_ACPI_ASYNC_EVAL_METHOD can be used only at IRQL <= DISPATCH_LEVEL.

Requirements

Version

Windows Vista and later versions of Windows.

Header

Acpiioctl.h (include Acpiioctl.h)

See also

ACPI_EVAL_INPUT_BUFFER
ACPI_EVAL_INPUT_BUFFER_COMPLEX
ACPI_EVAL_INPUT_BUFFER_SIMPLE_INTEGER
ACPI_EVAL_INPUT_BUFFER_SIMPLE_STRING
ACPI_EVAL_OUTPUT_BUFFER
ACPI_METHOD_ARGUMENT
IOCTL_ACPI_EVAL_METHOD
IOCTL_ACPI_EVAL_METHOD_EX

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft. All rights reserved.