Interrupt Handling Functions (Compact 2013)
3/26/2014
The following table describes the Windows Embedded Compact 2013 functions that device driver developers typically use to implement device driver interrupt handling functionality.
Function |
Description |
|---|---|
Disables a hardware interrupt that its interrupt handler specifies. |
|
Signals to the kernel that interrupt processing is complete. |
|
Initializes a hardware interrupt with the kernel. This initialization allows the device driver to register an event and enable the interrupt. |
|
Associates an interrupt service routine (ISR) with an interrupt request (IRQ). You call this function from within OEMInit to make this association. |
|
Breaks the association between an ISR and an IRQ. |
|
Creates a named or unnamed event object. |
|
Allows a device driver to cause an artificial interrupt event. |
|
Sets the state of the specified event object to signaled. |
|
Sets the state of the specified event object to nonsignaled. |
|
Provides a single operation that sets the state of the specified event object to signaled, and then resets it to nonsignaled after releasing the appropriate number of waiting threads. |
|
Returns when the specified object is in the signaled state or when the time-out interval elapses. The kernel provides special treatment for interrupt events. Interrupt service threads (ISTs) cannot use WaitForMultipleObjects with an interrupt event. |
|
Signals events during suspend or resume. Power handlers call this function. |
For more information about these functions, see the reference information for each function.