WDF Interrupt Issue

[Murugesan]

Hi all,

I am working with a PCI based WDF function driver. I've created an
interrupt object using wdfinterruptcreate() & initialized the
WDF_INTERRUPT_CONFIG with ISR handler, DPC routine. From the WDF
documentation, i found that the framework takes care of adding interrupt
resource information when the device moves into D0 state. Now the problem is,
after doing all this initialization my interrupt handler doesn't gets invoked
when my hardware raises an interrupt after the device moves into D0 state
eventhough all the interrupts has been enabled. I could notice that the
framework has added the interrupt resource information to the interrupt
object, by using WdfInterruptGetInfo() in the context of SelfManagedIoInit
callback. Am I missing anything related with the interrupt handling?

Thanks,
Murugesan

[eagersh]

On Nov 10, 11:53 am, Murugesan <Muruge...@discussions.microsoft.com>
wrote:

Are you sure that your hardware generate interrupt? You should check
it by using PCI Bus analyzer.
You could also check if your device get PCI resources, including
Interrupt, by using WinDbg command !pci.

Igor Sharovar

[Doron Holan [MSFT]]

are your programming your hw to generate the interrupt and route it
correctly? are you programming your hw correctly in D0Entry?

d

--

This posting is provided "AS IS" with no warranties, and confers no rights.

"Murugesan" <Muru...@discussions.microsoft.com> wrote in message
news:70DE1BF5-1409-408C...@microsoft.com...

[Murugesan]

Thanks for your inputs. I've programmed my h/w correctly. The only variance
is like,
my h/w initialization & enabling interrupts has been done in the context of
SelfManagedIoInit() callback, which is called after D0entry callback. Also i
am sure that the framework retreived the interrupt resource
information(mainly IRQ) by checking with WdfInterruptGetInfo().

Murugesan

"Doron Holan [MSFT]" wrote:

> .
>

[Doron Holan [MSFT]]

you should use EvtInterruptEnable and EvtDeviceD0EntryPostInterruptsEnabled
for the work you are doing in self managed io

d

--

This posting is provided "AS IS" with no warranties, and confers no rights.

"Murugesan" <Muru...@discussions.microsoft.com> wrote in message

news:7FE38A6D-FFDE-4D59...@microsoft.com...

[Murugesan]

Actually I am interested in performing initialization of h/w first, only
after which interrupt enabling comes into picture. That's why I did
everything in selfmanaged-io, instead of collapsing my sequence of operation
b/w EvtInterruptEnable, EvtDeviceD0EntryPostInterruptsEnabled & Selfmanaged
IO.

Does failing to enable interrupts in EvtInterruptEnable or
EvtDeviceD0EntryPostInterruptsEnabled callbacks makes the interrupt handler
not to be invoked ? Do they really have any relation ?

"Doron Holan [MSFT]" wrote:

> .
>

[Doron Holan [MSFT]]

the kmdf callbacks are just an abstraction, you can choose to use the
abstraction or not. if you need to initialize before the interrupt is
enabled, do that in EvtDeviceD0Entry, enable the interrupt in
EvtInterruptEnable

d

--

This posting is provided "AS IS" with no warranties, and confers no rights.

"Murugesan" <Muru...@discussions.microsoft.com> wrote in message

news:D20534EA-16EB-472D...@microsoft.com...

[Murugesan]

Thanks for your info Doron. I'll try that.

"Doron Holan [MSFT]" wrote:

> .
>