| UID | title | description | old-location | ms.date | keywords | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | tech.root | req.typenames | f1_keywords | topic_type | api_type | api_location | api_name | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NS:d3dkmddi._DXGK_INHERITED_TIMING_INFO |
_DXGK_INHERITED_TIMING_INFO (d3dkmddi.h) |
Structure passed to the driver in the pPrivateDriverData argument of DxgkDdiRecommendFunctionalVidPn, which the driver should use to describe the color space and wire format which cannot be described easily in the VidPn the DDI builds. |
display\dxgk_inherited_timing_info.htm |
05/10/2018 |
|
*PDXGK_INHERITED_TIMING_INFO, DXGK_INHERITED_TIMING_INFO, DXGK_INHERITED_TIMING_INFO structure [Display Devices], PDXGK_INHERITED_TIMING_INFO, PDXGK_INHERITED_TIMING_INFO structure pointer [Display Devices], _DXGK_INHERITED_TIMING_INFO, d3dkmddi/DXGK_INHERITED_TIMING_INFO, d3dkmddi/PDXGK_INHERITED_TIMING_INFO, display.dxgk_inherited_timing_info |
d3dkmddi.h |
Windows |
Windows |
display |
DXGK_INHERITED_TIMING_INFO, *PDXGK_INHERITED_TIMING_INFO |
|
|
|
|
|
Structure passed to the driver in the pPrivateDriverData argument of DxgkDdiRecommendFunctionalVidPn, which the driver should use to describe the color space and wire format which cannot be described easily in the VidPn the DDI builds
A D3DDDI_COLOR_SPACE_TYPE value which describes the output color space currently being applied for the transported pixels. The driver is responsible for sending appropriate metadata to ensure the display device is set up to interpret pixels correctly for this color space.
A D3DKMDT_WIRE_FORMAT_AND_PREFERENCE value which indicates the wire format which is actually being used. Although the target mode pinned in the VidPn returned by the call to DxgkDdiRecommendFunctionalVidPn could be required to describe exactly one wire format, that might require the driver to prepare a special target mode just for the boot case. Instead, this field should be used to report the current wire color encoding format and bits per color channel. Whichever format is reported in this field should also have been reported as supported in the target mode reported through DxgkDdiRecommendFunctionalVidPn.
A DXGK_GLITCH_CAUSE value which indicates what underlying change or changes in the display pipeline caused a user perceptible glitch.
A DXGK_GLITCH_EFFECT value which indicates what the glitch looked like to a user.
A DXGK_GLITCH_DURATION value which indicates approximately how long the glitch lasted. Note, this is intended to reflect how long the underlying issue was present but the visible effect may be longer in some cases. For example, when sync is lost long enough for a monitor to have to redetect, the display device will likely take many frames to recover. It is the length of the underlying issue which should be reported, not the recovery time as that will vary between devices.
This value is reserved for system use.
Set of information filled out by the driver for the boot display to describe any side-effects of the DxgkDdiStartDevice.
In many cases, glitches are inevitable so these fields attempt to understand the underlying cause and the extend of the user impact. OEMs and customers often complain about glitches during boot so having the driver report the glitch to the OS should help to investigate such issues quickly.