WdfPdoAddEjectionRelationsPhysicalDevice - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// wdfpdo.h
NTSTATUS WdfPdoAddEjectionRelationsPhysicalDevice(
[in] WDFDEVICE Device,
[in] PDEVICE_OBJECT PhysicalDevice
);
View the official Windows Driver Kit DDI referenceNo description available.
[Applies to KMDF only]
The WdfPdoAddEjectionRelationsPhysicalDevice method indicates that a specified device is ejected when another specified device is ejected.
Device [in]A handle to a framework device object.
PhysicalDevice [in]A pointer to a caller-supplied DEVICE_OBJECT structure that represents a physical device object (PDO).
If the operation succeeds, the method returns STATUS_SUCCESS. Additional return values include:
| Return code | Description |
|---|---|
| STATUS_INVALID_PARAMETER | An input parameter is NULL. |
| STATUS_INSUFFICIENT_RESOURCES | A memory allocation failed. |
The method might also return other NTSTATUS values.
A system bug check occurs if the driver supplies an invalid object handle.
The PhysicalDevice parameter points to a PDO of a device that is ejected when the device that is identified by Device is ejected. Typically, both devices are controlled by the calling driver. Do not report the child devices of Device because when the PnP manager ejects a parent device, it also ejects the device's children.
For more information, see Supporting Ejectable Devices.
The following code example adds a device that the pPhysicalDeviceObject structure represents to the list of devices that are ejected when the device that device specifies is ejected.
PDEVICE_OBJECT pPhysicalDeviceObject;
NTSTATUS status;
...
status = WdfPdoAddEjectionRelationsPhysicalDevice(
device,
pPhysicalDeviceObject
);
WdfPdoClearEjectionRelationsDevices
WdfPdoRemoveEjectionRelationsPhysicalDevice