PCIe bus seems work while 'dma' can't under linux
Benjamin Herrenschmidt
benh at kernel.crashing.org
Tue Jun 15 17:12:42 EST 2010
On Tue, 2010-06-15 at 15:05 +0800, jxnuxdy wrote:
> Thanks Benjamin, the regions don't display as what we expect, that's why we suspect if there any configuration probelms in CPU host bridge, but we changed the uboot/linux a lot, seems take no effect on that problems.
>
> We use CPU MPC8544, and connect two PCIE devices to CPU PCIE1 and PCIE2 directly without a extended PCIE bridge, so we disabled PCIE3 and PCI controlers in uboot level.
>
> More settings pls take a look at the attach file log.txt.
I'm not familiar with those freescale parts, so I'll let others comment
on your settings since it's most likely to be where the problem is.
Cheers,
Ben.
>
> Many thanks,
> Denny
> ----------------------------------------------------------------------------------------------------------------------------
> 在2010-06-11 15:21:24，"Benjamin Herrenschmidt" <benh at kernel.crashing.org> 写道：
> >On Fri, 2010-06-11 at 09:30 +0800, jxnuxdy wrote:
> >> Hi guys,
> >>
> >> I encountered a PCIe problem under linux, the two PCIe bus on my board seems work,
> >> at least I can access the registers through the PCIe bus, however the dma for the
> >> PCIe bus can't work, so I just dumped the pci device, but I am curiously to find
> >> there is no regions displayed on PCIe controlers, why? is it relate with my 'dma' issue then?
> >
> >It would help if you told us a bit more what the HW is, what you are
> >doing with it, etc...
> >
> >IE. What is your host, what is your device, what platform, etc...
> >
> >DMA should work provided that your platform code sets it up properly.
> >The DMA regions don't appear in /proc/pci or lspci.
> >
> >Cheers,
> >Ben.
> >
> >>
> >> bash-2.04# cat /proc/pci
> >> PCI devices found:
> >> Bus 0, device 0, function 0:
> >> Class 0b20 Header Type 01: PCI device 1957:0032 (rev 17).
> >> Bus 1, device 0, function 0:
> >> Class 0580 Header Type 00: PCI device 11ab:db90 (rev 1).
> >> Prefetchable 64 bit memory at 0x80000000 [0x800fffff].
> >> Prefetchable 64 bit memory at 0x84000000 [0x87ffffff].
> >> Bus 9, device 0, function 0:
> >> Class 0b20 Header Type 01: PCI device 1957:0032 (rev 17).
> >> Bus 10, device 0, function 0:
> >> Class 0580 Header Type 00: PCI device 11ab:db90 (rev 1).
> >> Prefetchable 64 bit memory at 0xa0000000 [0xa00fffff].
> >> Prefetchable 64 bit memory at 0xa4000000 [0xa7ffffff].
> >> bash-2.04# lspci -vv
> >> 00:00.0 Power PC: Unknown device 1957:0032 (rev 11)
> >> !!! Invalid class 0b20 for header type 01
> >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> >> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> >> Latency: 0, cache line size 08
> >> Bus: primary=00, secondary=01, subordinate=06, sec-latency=0
> >> I/O behind bridge: 00000000-00000fff
> >> Memory behind bridge: 80000000-9fffffff
> >> BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
> >> Capabilities: [44] Power Management version 2
> >> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
> >> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >> Capabilities: [4c] #10 [0041]
> >>
> >> 01:00.0 Memory controller: Galileo Technology Ltd.: Unknown device db90 (rev 01)
> >> Subsystem: Galileo Technology Ltd.: Unknown device 11ab
> >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> >> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> >> Latency: 0, cache line size 08
> >> Interrupt: pin A routed to IRQ 0
> >> Region 0: Memory at 80000000 (64-bit, prefetchable) [size=1M]
> >> Region 2: Memory at 84000000 (64-bit, prefetchable) [size=64M]
> >> Capabilities: [40] Power Management version 2
> >> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> >> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >> Capabilities: [50] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
> >> Address: 0000000000000000 Data: 0000
> >> Capabilities: [60] #10 [0011]
> >>
> >> 09:00.0 Power PC: Unknown device 1957:0032 (rev 11)
> >> !!! Invalid class 0b20 for header type 01
> >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> >> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> >> Latency: 0, cache line size 08
> >> Bus: primary=00, secondary=0a, subordinate=0f, sec-latency=0
> >> I/O behind bridge: 00000000-00000fff
> >> Memory behind bridge: a0000000-bfffffff
> >> BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
> >> Capabilities: [44] Power Management version 2
> >> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
> >> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >> Capabilities: [4c] #10 [0041]
> >>
> >> 0a:00.0 Memory controller: Galileo Technology Ltd.: Unknown device db90 (rev 01)
> >> Subsystem: Galileo Technology Ltd.: Unknown device 11ab
> >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> >> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> >> Latency: 0, cache line size 08
> >> Interrupt: pin A routed to IRQ 0
> >> Region 0: Memory at a0000000 (64-bit, prefetchable) [size=1M]
> >> Region 2: Memory at a4000000 (64-bit, prefetchable) [size=64M]
> >> Capabilities: [40] Power Management version 2
> >> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> >> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >> Capabilities: [50] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
> >> Address: 0000000000000000 Data: 0000
> >> Capabilities: [60] #10 [0011]
> >>
> >> bash-2.04#
> >>
> >> Thanks
> >> Denny
> >>
> >> _______________________________________________
> >> Linuxppc-dev mailing list
> >> Linuxppc-dev at lists.ozlabs.org
> >> https://lists.ozlabs.org/listinfo/linuxppc-dev
> >
> >
> >_______________________________________________
> >Linuxppc-dev mailing list
> >Linuxppc-dev at lists.ozlabs.org
> >https://lists.ozlabs.org/listinfo/linuxppc-dev
More information about the devicetree-discuss
mailing list