DXGKDDI_DSICAPS - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// dispmprt.h
DXGKDDI_DSICAPS DxgkddiDsicaps;
NTSTATUS DxgkddiDsicaps(
[in] HANDLE Context,
[in] D3DDDI_VIDEO_PRESENT_TARGET_ID TargetId,
[out] PDXGK_DSI_CAPS pArgs
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
The DxgkddiDsiCaps callback function queries the Display Serial Interface (DSI) capabilities for a particular target.
Context [in]As retrieved from the driver's MIPI interface (DXGK_MIPIDSI_interface ,_ DXGK queries the driver for this context.
TargetId [in]Target identifier of the monitor.
pArgs [out]Pointer to a DXGI_DSI_CAPS structure.
DxgkddiDsiCaps returns STATUS_SUCCESS if it succeeds; otherwise it returns one of the error codes defined in Ntstatus.h.
An OEM panel driver should initialize by sending IOCTL_MIPI_DSI_QUERY_CAPS which provides information to allow the OEM panel driver to verify driver support, and provides the raw level 1 DDB data from the display to allow one panel driver to support multiple devices and to confirm that there is no mismatch. The OS graphics kernel calls DxgkddiDsiCaps when it receives this IOCTL. The capabilities are returned in a DXGK_DSI_CAPS structure.
The graphics driver fills in the DXGI_DSI_CAPS fields, using cached information if available since the data should be static. Since the OS needs theTargetMaximumReturnPacketSize field value for packet validation, it can request the capabilities from the graphics driver before receiving a request from the panel driver.
The OEM panel driver is responsible for validating DSI capability and compatibility with the panel, since neither the graphics driver nor the OS has sufficient information to do so, particularly for any manufacturer defined or undefined elements.