MSI and Internal MSI-X Interrupts - 3.0 English

AXI Bridge for PCI Express Gen3 Subsystem Product Guide (PG194)

Document ID
PG194
Release Date
2022-11-16
Version
3.0 English
Note: Internal MSI-X Interrupt mode is only available in DMA/Bridge Subsystem for PCIe in Bridge Mode.
Asserting one or more bits of usr_irq_req causes the generation of an MSI or MSI-X interrupt if MSI or MSI-X is enabled. If both MSI and MSI-X capabilities are enabled, an MSI-X interrupt is generated. The Internal MSI-X interrupts mode is enabled when you set the MSI-X Implementation Location option to Internal in the PCIe Misc Tab.

After a usr_irq_req bit is asserted, it must remain asserted until the corresponding usr_irq_ack bit is asserted and the interrupt has been serviced and cleared by the Host. The usr_irq_ack assertion indicates the requested interrupt has been sent on the PCIe block. This will ensure the interrupt pending register within the IP remains asserted when queried by the Host's Interrupt Service Routine (ISR) to determine the source of interrupts. You must implement a mechanism in the user application to know when the interrupt routine has been serviced. This detection can be done in many different ways depending on your application and your use of this interrupt pin. This typically involves a register (or array of registers) implemented in the user application that is cleared, read, or modified by the Host software when an Interrupt is serviced.

Configuration registers are available to map usr_irq_req and DMA interrupts to MSI or MSI-X vectors. For MSI-X support, there is also a vector table and PBA table. The following figure shows the MSI interrupt.

This figure shows only the handshake between usr_irq_req and usr_irq_ack . Your application might not clear or service the interrupt immediately, in which case, you must keep usr_irq_req asserted past usr_irq_ack .

Figure 1. MSI Interrupts

The following figure shows the MSI-X interrupt.

This figure shows only the handshake between usr_irq_req and usr_irq_ack . Your application might not clear or service the interrupt immediately, in which case, you must keep asserted past usr_irq_ack .

Figure 2. MSI-X Interrupts