How to communicate with another driver from ISR of a driver

NTDEV
1

Hi,
I need to write two drivers… Say Driver1 and Driver2. Driver1 talks to
an external hardware thro PCI bus. Driver2 handles the Interface
part.(processes the interrupts from the external hardware) I need Driver2 to
inform Driver1 in case of an interrupt by some means…I know i cannot use
events since i cant set events in ISR. I would like to know how i can
implement this…
TIA.

Vijay

2

  1. With rather elastic latency you can always do your signalling from a
    dpc routine rather than an isr. Either complete IRPs or set events
    signalled in the Driver2 DPC routine.

  2. You can create private function call interfaces between driver1 and
    driver2 and simply call into driver1 from the driver2 isr. Driver1 will
    then be executing at DIRQL, and this will probably cause you other
    headaches, so I suggest (1) above as the more normal solution.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Vijay
Sent: Monday, May 13, 2002 5:59 AM
To: NT Developers Interest List
Subject: [ntdev] How to communicate with another driver from
ISR of a driver

Hi,
I need to write two drivers… Say Driver1 and Driver2.
Driver1 talks to an external hardware thro PCI bus. Driver2
handles the Interface part.(processes the interrupts from the
external hardware) I need Driver2 to inform Driver1 in case
of an interrupt by some means…I know i cannot use events
since i cant set events in ISR. I would like to know how i
can implement this… TIA.

Vijay

You are currently subscribed to ntdev as:
xxxxx@hollistech.com To unsubscribe send a blank email to
%%email.unsub%%

3

You can register some system service in KeServiceDescriptorTable from
Driver1 and save it’s number ,and you can call that function from Driver2.