| 1 |
=============== |
| 2 |
What is an IRQ? |
| 3 |
=============== |
| 4 |
|
| 5 |
An IRQ is an interrupt request from a device. Currently, they can come |
| 6 |
in over a pin, or over a packet. Several devices may be connected to |
| 7 |
the same pin thus sharing an IRQ. Such as on legacy PCI bus: All devices |
| 8 |
typically share 4 lanes/pins. Note that each device can request an |
| 9 |
interrupt on each of the lanes. |
| 10 |
|
| 11 |
An IRQ number is a kernel identifier used to talk about a hardware |
| 12 |
interrupt source. Typically, this is an index into the global irq_desc |
| 13 |
array or sparse_irqs tree. But except for what linux/interrupt.h |
| 14 |
implements, the details are architecture specific. |
| 15 |
|
| 16 |
An IRQ number is an enumeration of the possible interrupt sources on a |
| 17 |
machine. Typically, what is enumerated is the number of input pins on |
| 18 |
all of the interrupt controllers in the system. In the case of ISA, |
| 19 |
what is enumerated are the 8 input pins on each of the two i8259 |
| 20 |
interrupt controllers. |
| 21 |
|
| 22 |
Architectures can assign additional meaning to the IRQ numbers, and |
| 23 |
are encouraged to in the case where there is any manual configuration |
| 24 |
of the hardware involved. The ISA IRQs are a classic example of |
| 25 |
assigning this kind of additional meaning. |