UdecxWdfDeviceTryHandleUserIoctl - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// udecxwdfdevice.h
BOOLEAN UdecxWdfDeviceTryHandleUserIoctl(
WDFDEVICE UdecxWdfDevice,
[in] WDFREQUEST Request
);
View the official Windows Driver Kit DDI referenceNo description available.
Attempts to handle an IOCTL request sent by a user-mode software.
UdecxWdfDeviceA handle to a framework device object that represents the controller. The client driver initialized this object in the previous call to UdecxWdfDeviceAddUsbDeviceEmulation.
Request [in]A handle to a framework request object that represents the IOCTL request.
TRUE indicates that USB device emulation class extension (UdeCx) recognized and completed the request (with success or failure). In this case, the client driver must not complete the request. FALSE otherwise; the driver must complete the request.
The UDE client driver presents itself to user-mode software as a host controller driver. The client driver registers and exposes the GUID_DEVINTERFACE_USB_HOST_CONTROLLER device interface GUID. User-mode software can open a handle to the device by specifying that GUID. By using that handle, the software can send IOCTL requests.
Note Note that other interface's IOCTL codes may overlap with the USB host controller interface. If such I/O reaches this function the IOCTL will not be handled correctly.
The client driver does not need to process the received IOCTL. It can send the request to the class extension by calling UdecxWdfDeviceTryHandleUserIoctl. If the class extension recognizes the request as a standard request, it completes it. Otherwise, the call fails and the client driver is then expected to complete the request. For a list of IOCTLs that must be handled, see USB IOCTLs for applications and services.
Architecture: USB Device Emulation (UDE)