VIDEO_POWER_MANAGEMENT - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// ntddvdeo.h
typedef struct _VIDEO_POWER_MANAGEMENT {
ULONG Length;
ULONG DPMSVersion;
ULONG PowerState;
} VIDEO_POWER_MANAGEMENT, *PVIDEO_POWER_MANAGEMENT;
View the official Windows Driver Kit DDI referenceNo description available.
The VIDEO_POWER_MANAGEMENT structure contains information required by the miniport driver to perform power management.
LengthIs the size in bytes of this VIDEO_POWER_MANAGEMENT structure.
DPMSVersionSpecifies the version of the Display Power Management Signaling (DPMS) standard supported by the device. Currently, the video port driver sets this member to zero, which corresponds with Version 1.0 of the VESA DPMS Standard.
PowerStateSpecifies the power management state to be set or queried. This member can be one of the following values in the VIDEO_POWER_STATE enumeration:
The monitor and graphics adapter are both fully powered on and operational.
The monitor is running at a reduced power level that requires a short recovery time to VideoPowerOn. The graphics adapter is powered on (registers are still active and video memory is refreshed); however, clocks might be lost.
The monitor is running at a substantially reduced power level that requires a possibly longer recovery time than VideoPowerStandBy to VideoPowerOn. The graphics adapter is off.
The monitor and graphics adapter are both off, consuming no power at all.
The monitor and graphics adapter are both fully powered on and operational.
The video port driver allocates and fills in the VIDEO_POWER_MANAGEMENT structure. Depending on the power management request dispatched to the video port, the video port driver passes this structure to the miniport driver's HwVidGetPowerState or HwVidSetPowerState routine.
VideoPowerHibernate is provided to the miniport driver as notification only. The miniport driver's HwVidSetPowerState function must leave the monitor and graphics adapter fully powered on and operational. For all other states, the miniport driver must put the device into the specified power state.
A driver will always enter all other power states from the VideoPowerOn state. For example, a driver will not move directly to VideoPowerHibernate from VideoPowerOff; it will always go from VideoPowerHibernate to VideoPowerOn and then to VideoPowerOff.