SPRUIE9D May 2017 – May 2024 DRA74P , DRA75P , DRA76P , DRA77P
The ISS merges the interrupt sources listed in Table 9-5 into six physical interrupt lines (ISS_IRQ0 to ISS_IRQ5). All six lines support level and pulse modes.
Interrupt(1) | Source | Description |
---|---|---|
ISP_IRQ[3:0] | ISP | Interrupts generated by the ISP |
CAL_B_IRQ | CAL_B | Interrupt generated by the CAL_B receiver |
SIMCOP_IRQ[3:0] | SIMCOP | Interrupts generated by SIMCOP |
Software can select which interrupt sources are routed to each output line (ISS_IRQ[0:5]). All six physical interrupt outputs have equivalent functions. Software can use different interrupt lines to group events together by type and therefore reduce interrupt latencies. Typically, one interrupt line is used for low-priority events (errors), and the other interrupt lines are used for high-priority events (for example, SIMCOP sequencing and end-of-frame events to trigger configuration load). The ISS internal interrupt request (IRQ) merger (see Figure 9-3) relies only on level interrupts provided by submodules. Pulse interrupts provided by submodules are ignored. All of the interrupts are routed to device interrupt crossbar. Software does not need to clear events from submodules at the ISS level: it clears only the events at the submodule level. The IRQ merger automatically clears the IRQ at ISS level (events generated by sub-modules are automatically cleared at ISS level when they are cleared at sub-module level).
For more information about the mapping of the six lines to the device modules outside ISS, see Table 9-3.
The ISP, SIMCOP, CAL_B, and HL ISS merger IRQ lines are configurable. Each interrupt can be mapped to the required line.