DXGKDDI_CONTROLINTERRUPT2 - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3dkmddi.h
DXGKDDI_CONTROLINTERRUPT2 DxgkddiControlinterrupt2;
NTSTATUS DxgkddiControlinterrupt2(
[in] IN_CONST_HANDLE hAdapter,
[in] IN_CONST_DXGKARG_CONTROLINTERRUPT2 InterruptControl
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
The DxgkDdi_ControlInterrupt2 function enables or disables the given interrupt type on the graphics hardware.
hAdapter [in]A handle to the adapter object for the graphics processing unit (GPU). The driver returned this handle in the MiniportDeviceContext parameter from a call to its DxgkDdiAddDevice function.
InterruptControl [in]A DXGKARG_CONTROLINTERRUPT2 structure that supplies the interrupt type, as well as the VSYNC state.
DxgkDdi_ControlInterrupt2 returns one of the following values:
| Return code | Description |
|---|---|
| STATUS_SUCCESS | The interrupt type was successfully enabled or disabled on the graphics hardware. |
| STATUS_NOT_IMPLEMENTED | DxgkDdi_ControlInterrupt2 does not support enabling or disabling the specified interrupt type. |
Only one of DxgkDdiControlInterrupt2 or DxgkDdi_ControlInterrupt3 will be used by the OS during the lifetime of an adapter.
WDDM 2.7 drivers that do not implement DxgkDdi_ControlInterrupt3 are opting out of independent VidPn VSync control, and the OS will only call DxgkDdi_ControlInterrupt2. The DXGK_DRIVERCAPS->IndependentVidPnVSync capability must be 0 in drivers that do not support DxgkDdi_ControlInterrupt3; otherwise, the OS will fail adapter initialization. If driver does implement DxgkDdi_ControlInterrupt3, then the capability can be set to 0 or 1 to indicate Per-VidPn support.