cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
5,462 Views
Registered: ‎01-06-2011

PCIe endpoint block plus v1.14 legacy interrupt

Hi,

 

Just to check if I send configuration command to endpoint to send legacy interrupt to root port, what is the response from root port? Can I see anything from the RTL simulation? Will any of the configuration registers reflect the interrupt status? Thanks

 

 

 

Regards

AYE

0 Kudos
3 Replies
gszakacs
Professor
Professor
5,455 Views
Registered: ‎08-14-2007

My understanding of the "Legacy" interrupt is that you treat it like a level-triggered interrupt

from the old (legacy) PCI bus.  On PCIe, there is a signal sent to the root port to say you

are asserting the interrupt, and another you send to say you are de-asserting the interrupt.

There is no "interrupt acknowledge" from the root port.  It is up to the software that

handles the interrupt to send a signal back to your interrupting device to say that

the interrupt has been handled.  Usually this is implemented as a register write

to the interrupting device's register space.  This write would then signal your

logic to de-assert the interrupt.  There are other approaches as well.  For example you

may have a FIFO collecting serial input data and assert the interrupt whenever the

FIFO is not empty.  When the root port has read all elements of the FIFO, then the

interrupt would be de-asserted.

 

HTH,

Gabor

-- Gabor
0 Kudos
5,413 Views
Registered: ‎01-06-2011

Hi,

 

Thanks for your explanation. So the configuration space will not have a bit to signal that the endpoint has assert the legacy interrupt? Thanks

 

 

Regards

AYE

0 Kudos
luisb
Xilinx Employee
Xilinx Employee
5,400 Views
Registered: ‎04-06-2010

The PCI Configuration Space should assert the interrupt status bit of the status register when a legacy interrupt is asserted.   This is bit 3 of the status register.  You can find this information in the PCI Spec.  Once the deassert packet is sent, that's when this same bit gets cleared.  The root shouldn't have to do anything.

 

The unfortunate news is that this is not functioning correctly as described in the following answer record:

http://www.xilinx.com/support/answers/31210.htm

0 Kudos