Add Interrupt Handling Functionality (Compact 2013)
3/26/2014
Most peripheral devices generate interrupts to receive service from the OS. Because these peripheral devices can cause or signal interrupts, their device drivers must process interrupts to service their devices. Devices generate interrupts by using physical interrupt request (IRQ) lines. An IRQ line is a hardware line over which a device can send an interrupt signal to the microprocessor. A system interrupt (SYSINTR), which is also known as a logical interrupt, is a mapping of an IRQ as specified by the OEM adaptation layer (OAL). For more information about the OAL, see BSP Components and Code Organization.
A typical Windows Embedded Compact 2013 device driver separates interrupt handling into two components:
- An interrupt service routine (ISR)
- An interrupt service thread (IST)
The following sections describe these components in more detail.
In This Section
- Interrupt Service Routines
Describes the tasks that ISRs perform.
- Interrupt Service Threads
Describes the tasks that ISTs perform.
- Service Interrupts
Describes the sequence of events that typically occurs during interrupt handling.
- Register Your Interrupt Service Routine
Describes the interrupt handler registration process.
- Handle Nested Interrupts
Describes how Windows Embedded Compact handles nested ISR calls.
- Handle Shared Interrupts
Describes how Windows Embedded Compact handles shared interrupts.
- Interrupt Handling Functions
Lists the functions that typically provide interrupt handling functionality.