Add PCIe support for i.MX6q
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v7 Latest posting 11/110 of 2 patches 0 repliesNew
- v7 posting 10/110 of 2 patches 0 repliesSuperseded
- v7 posting 9/110 of 2 patches 0 repliesSuperseded
Earlier versions · 8
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v7 posting 8/11 | 0 of 2 patches | 0 replies | Superseded | |
| v7 posting 7/11 | 0 of 2 patches | 0 replies | Superseded | |
| v7 posting 6/11 | 0 of 2 patches | 0 replies | Superseded | |
| v7 posting 5/11 | 0 of 2 patches | 0 replies | Superseded | |
| v7 posting 4/11 | 0 of 2 patches | 0 replies | Superseded | |
| v7 posting 3/11 | 0 of 2 patches | 0 replies | Superseded | |
| v7 posting 2/11 | 0 of 2 patches | 0 replies | Superseded | |
| v7 posting 1/11 | 2 patches | 0 replies | Superseded |
Patches in v7 posting 11/11 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v7 yet.
Cover letter [PATCH v7 0/2] Add PCIe support for i.MX6q
Hi Richard,
Quoted 4 lines
Hi Tim:
As I know that the clock of pcie controller should be always running. There are not clock gate on/off operations in host driver after the initialization.
I think the problem might happen when the PCIe device (Ethernet adapter) is bus- master and either initiates PCIe->AXI->memory write or memory->AXI->PCIe read transfer. This is because when the Intel ethernet (igb) is probed, it only uses the MEM window that's mapped into the AXI space (that window at 0x01100000). On the other hand, when some packet is transfered, the Intel controller operates with structures in DRAM directly. And the stall only happens when the interface either receives or attempts to send a packet.
Is this theory of mine even reasonable? If this doesn't work properly, could this stall the CPU? How can I check if this works correctly? What can I try if it does not?
Thanks!
btw. Please be careful about the top-posting ;-)
Best regards,
Marek Vasut