PEP_WORK_ACTIVE_COMPLETE - NtDoc

Native API online documentation, based on the System Informer (formerly Process Hacker) phnt headers 
// pep_x.h

typedef struct _PEP_WORK_ACTIVE_COMPLETE {
       POHANDLE DeviceHandle;
  [in] ULONG    Component;
} PEP_WORK_ACTIVE_COMPLETE, *PPEP_WORK_ACTIVE_COMPLETE;
View the official Windows Driver Kit DDI reference

NtDoc

No description available.

Edit description on GitHub

Windows Driver Kit DDI reference (ns-pep_x-_pep_work_active_complete)

_PEP_WORK_ACTIVE_COMPLETE structure

Description

The PEP_WORK_ACTIVE_COMPLETE structure identifies a component that is now in the active condition.

Members

DeviceHandle

A 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.

Remarks

The ActiveComplete member of the PEP_WORK_INFORMATION structure is a PEP_WORK_ACTIVE_COMPLETE structure.

See also

PEP_DEVICE_REGISTER_V2

PEP_DPM_REGISTER_DEVICE

PEP_WORK_INFORMATION

View the official Windows Driver Kit DDI reference

Edit description on GitHub