WDF_RETRIEVE_CHILD_FLAGS - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// wdfchildlist.h
typedef enum _WDF_RETRIEVE_CHILD_FLAGS {
WdfRetrieveUnspecified = 0x0000,
WdfRetrievePresentChildren = 0x0001,
WdfRetrieveMissingChildren = 0x0002,
WdfRetrievePendingChildren = 0x0004,
WdfRetrieveAddedChildren = (WdfRetrievePresentChildren | WdfRetrievePendingChildren),
WdfRetrieveAllChildren = (WdfRetrievePresentChildren | WdfRetrievePendingChildren | WdfRetrieveMissingChildren)
} WDF_RETRIEVE_CHILD_FLAGS;
View the official Windows Driver Kit DDI referenceNo description available.
[Applies to KMDF only]
The WDF_RETRIEVE_CHILD_FLAGS enumeration defines flags that a driver can set before calling WdfChildListBeginIteration.
WdfRetrieveUnspecified:0x0000Reserved for internal use only.
WdfRetrievePresentChildren:0x0001Calls to WdfChildListRetrieveNextDevice will retrieve child devices for which a framework device object exists.
WdfRetrieveMissingChildren:0x0002Calls to WdfChildListRetrieveNextDevice will retrieve child devices that are marked as missing.
WdfRetrievePendingChildren:0x0004Calls to WdfChildListRetrieveNextDevice will retrieve child devices that the driver has reported as present, but for which a framework device object has not been created (because the framework has not called the driver's EvtChildListCreateDevice callback function).
WdfRetrieveAddedChildren:(WdfRetrievePresentChildren | WdfRetrievePendingChildren)Calls to WdfChildListRetrieveNextDevice will retrieve child devices that are present or pending.
WdfRetrieveAllChildren:(WdfRetrievePresentChildren | WdfRetrievePendingChildren | WdfRetrieveMissingChildren)Calls to WdfChildListRetrieveNextDevice will retrieve child devices that are present, pending, or missing.
Before calling WdfChildListBeginIteration, your driver must set WDF_RETRIEVE_CHILD_FLAGS-typed flags in a WDF_CHILD_LIST_ITERATOR structure.
WdfChildListRetrieveNextDevice