I understand from the documentation that this call can’t be made if the driver is not a power policy owner. What (technique) is the equivalent of this call for a rawpdo to prevent
the parent device from entering idle while its processing an ioctl? The parent device is also not a power policy owner
You left out a little bit of relevant information related to roles and state. What type of driver are you writing? From your description, it is a filter driver that enumerates a raw PDO. Is that correct? What is the device class that the filter is installed in? Usually the pattern enumerating a raw PDO from a filter is due to the inability to open the filter directly, where the keyboard and mouse class are the usual classes where a filter does this.
Hi Doron, yes, fd and its a usb device.
“it is a usb device” is not an answer to the “what device class is the filter driver installed in?” What device class is your filter installed in? To help you out, what does the Class= line look like in the [Version] section of your filter’s INF?
It is a custom sensor device and we don’t own the function driver but have access to device spec etc.
Is it a custom function driver or inbox? Regardless, you need to poke the function driver to power up the device/keep it from idling. Typically this means sending io to the function driver to perform the operation you want to execute. The function driver will then power up (if idle) to process the IO request.
Makes sense. Will give it a try. Thx