Skip to contentSkip to conversation

About use case of cdns3-pci-wrap.c

DISCUSSION Peter Chen 2 participants 2 messages Mar 27, 2021 – Mar 30, 2021 USB

lore
Share & tools
lore

Peter Chen

author
#0 lore raw

Hi Pawel,

From the code of this file, it seems the controller driver is running at PC side, but the hardware controller is at verification board, the two sides are connected by PCIe. Am I right?

If I am right, the memory (eg, the TRB ring address and data buffer) the hardware try to visit is at PC side, but how controller visits PC memory since the TRB ring address is allocated dynamically by controller device driver running at PC? How the local bus arbiter knows it is PCIe address at verification board? Besides, could the upstream code run this IP verification solution through PCIe without changing any code?

Thanks.

Signature · 2 lines
Thanks,
Peter Chen
#1 lore raw

Hi Peter,

Quoted 7 lines

Hi Pawel,

From the code of this file, it seems the controller driver is running at PC side, but the hardware controller is at verification board, the two sides are connected by PCIe. Am I right?

Quoted 6 lines

If I am right, the memory (eg, the TRB ring address and data buffer) the hardware try to visit is at PC side, but how controller visits PC memory since the TRB ring address is allocated dynamically by controller device driver running at PC? How the local bus arbiter knows it is PCIe address at verification board? Besides, could the upstream code run this IP verification solution through PCIe without changing any code?

Yes, the two sides, verification board and PC are connected by PCIe cable connected by using special PCIe adapters.
The PC sees FPGA board as the part of PC hardware. It's work in the same way as standard XHCI controller based on PCIe.

Quoted 7 lines

Thanks.

--

Thanks,
Peter Chen

Regards,
Pawel Laszczak