PEP_WORK_IDLE_STATE - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// pep_x.h
typedef struct _PEP_WORK_IDLE_STATE {
POHANDLE DeviceHandle;
[in] ULONG Component;
ULONG State;
} PEP_WORK_IDLE_STATE, *PPEP_WORK_IDLE_STATE;
View the official Windows Driver Kit DDI referenceNo description available.
The PEP_WORK_IDLE_STATE structure contains a request to transition a component to an Fx power state.
DeviceHandleA handle that represents the registration of the device with the Windows power management framework (PoFx). A POHANDLE value that represents the registration of the device with PoFx. The platform extension plug-in (PEP) previously received this handle from PoFx during the PEP_DPM_REGISTER_DEVICE notification that informed the PEP that the device's driver stack registered the device with PoFx.
Component [in]The index that identifies the component. This member is an index into the Components array in the PEP_DEVICE_REGISTER_V2 structure that the PEP previously supplied in response to the PEP_DPM_REGISTER_DEVICE notification for this device. If the Components array contains N elements, component indexes range from 0 to N–1.
StateThe target Fx power state to transition the component to. If this parameter is 0, the target state is F0; if this parameter is 1, the target state is F1; and so on. For more information about Fx power states, see Component-Level Power Management.
The IdleState member of the PEP_WORK_INFORMATION structure is a PEP_WORK_IDLE_STATE structure.