Message 2 of 3
16 Nov 17 19:20
Join Date: 08 Sep 2005
Posts To This List: 10157
Transition to D0?
Are you returning success from preparehardware? The first d0 entry is called by
the framework immediately after preparehw so returning failure after it is the
most likely cause. You can run !wdfkd.wdflogdump (your driver name) and see what
Bent from my phone
From: email@example.com on behalf of
Sent: Thursday, November 16, 2017 3:23:53 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Transition to D0?
I'm working on an driver for a custom FPGA PCIe card. This card is an early
version, and reportedly does not support PCIe power management features. I
suspect this lack of support in this early version is why my drivers
EVT_WDF_DEVICE_DO_ENTRY method is not being called. The add device is called
(where I'm looking at PCI config data) and Prepare hardware is called (where
I'm configuring the FPGA's BAR and etc) - but no D0 entry. Could this lack of
Power Support cause the the D0 state from not being entered? Can I artificially
inject ( as a temporary measure ) to force the driver to attain D0 state so it
can run? Currently my driver calls release hardware right after it calls
prepare hardware with no intervening D0 Entry callback called. Is there a way I
can opt out of power handling entirely and 'run' the driver?
Thanks for any ideas and guidance . .
NTDEV is sponsored by OSR
Visit the list online at:
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software
To unsubscribe, visit the List Server section of OSR Online at