Edit

DXGK_GRAPHICSPOWER_REGISTER_INPUT_V_1_2 structure (d3dkmthk.h)

  • Article

The DXGK_GRAPHICSPOWER_REGISTER_INPUT_V_1_2 structure is used to register the power state of a new input.

Syntax

typedef struct _DXGK_GRAPHICSPOWER_REGISTER_INPUT_V_1_2 {
  ULONG                         Version;
  PVOID                         PrivateHandle;
  PDXGK_POWER_NOTIFICATION      PowerNotificationCb;
  PDXGK_REMOVAL_NOTIFICATION    RemovalNotificationCb;
  PDXGK_FSTATE_NOTIFICATION     FStateNotificationCb;
  PDXGK_INITIAL_COMPONENT_STATE InitialComponentStateCb;
} DXGK_GRAPHICSPOWER_REGISTER_INPUT_V_1_2, *PDXGK_GRAPHICSPOWER_REGISTER_INPUT_V_1_2;

Members

Version

The current version being used. This value must be set to one of the following DXGK_GRAPHICSPOWER_VERSIONs:

#define DXGK_GRAPHICSPOWER_VERSION_1_0 0x1000
#define DXGK_GRAPHICSPOWER_VERSION_1_1 0x1001
#define DXGK_GRAPHICSPOWER_VERSION_1_2 0x1002
#define DXGK_GRAPHICSPOWER_VERSION DXGK_GRAPHICSPOWER_VERSION_1_2

By default, DXGK_GRAPHICSPOWER_VERSION represents the latest version. The graphics subsystem supports the current version and all previous versions. If this value is a version that isn't recognized, we will fail with STATUS_NOINTERFACE. This should only happen in the case the non-graphics driver was built for a newer OS than what is currently running, and in this case we expect the non-graphics driver to retry with a lower version number.

DXGK_GRAPHICSPOWER_VERSION_1_1 supports F-state change notifications. DXGK_GRAPHICSPOWER_VERSION_1_2 supports initial enumeration of shared power component data and state.

PrivateHandle

An opaque handle that will be provided in any callbacks. This handle must be globally unique, therefore, a pointer to the calling driver’s PDO or FDO should be used. This handle will be used as a key by graphics to track this specific registration, and will be associated with the non-graphics driver callbacks in order to handle their future removal.

PowerNotificationCb

A callback providing notification that the graphics device will be undergoing a device power state transition, and provide a new DEVICE_POWER_STATE. This callback is required to be implemented. See PDXGK_POWER_NOTIFICATION.

RemovalNotificationCb

A callback notifying that the graphics device is being removed. Any further callbacks into graphics for this DeviceHandle will return a failing NTSTATUS code and will be blocked until you return from the RemovalNotificationCb callback. This callback is required to be implemented. See PDXGK_REMOVAL_NOTIFICATION

FStateNotificationCb

Issues a state notification. This callback is optional, and is used by non-graphics drivers. See PDXGK_FSTATE_NOTIFICATION.

InitialComponentStateCb

Initializes the component state. See PDXGK_INITIAL_COMPONENT_STATE.

Remarks

Graphics drivers indicate what power components exist by responding to the queries DXGKQAITYPE_NUMPOWERCOMPONENTS and DXGKQAITYPE_POWERCOMPONENTINFO in _DXGK_QUERYADAPTERINFOTYPE.

If a graphics driver registers at least one DXGK_POWER_COMPONENT_SHARED component, a GRAPHICSPOWER interface will be created for that adapter. The interface will not be registered for adapters that do not expose any of these components.

Graphics drivers can register a “blocking” component by setting the DXGK_POWER_RUNTIME_COMPONENT flag ActiveInD3 to 0, or a “nonblocking” component by setting this flag to 1.

A blocking power component will prevent the graphics device from powering down when in use while a non-blocking power component will not. Both allow the graphics driver to properly manage its power planes when in-use by the non-graphics driver.

A graphics driver may expose both a blocking and non-blocking power component for a single physical/logical component, if it wishes to provide the ability for the non-graphics driver to selectively choose blocking or non-blocking usage.

When the GRAPHICSPOWER driver interface is available and enabled, a non-graphics driver can make an IO call to the graphics driver to register itself with the graphics driver providing and obtaining callbacks which will be used to manage the shared power components. The IO call will use the IOCTL_INTERNAL_GRAPHICSPOWER_REGISTER control code, with input data DXGK_GRAPHICSPOWER_REGISTER_INPUT_V_1_2 and output data _DXGK_GRAPHICSPOWER_REGISTER_OUTPUT.

Requirements

Requirement Value
Minimum supported client Windows 10, version 1803 (WDDM 2.4)
Header d3dkmthk.h