From: David Hawkins <dwh@ovro•caltech.edu>
To: Oliver Rutsch <orutsch@sympatec•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: MPC5200, PLX9054 PCI Card - stalled DMA transfers
Date: Thu, 01 Mar 2007 14:48:57 -0800 [thread overview]
Message-ID: <45E75859.3090508@ovro.caltech.edu> (raw)
In-Reply-To: <45E6CAC8.8090007@sympatec.com>
Oliver Rutsch wrote:
> Hi,
>
> we're using a TQM5200S-Module (MPC5200) on a STK52xx-board with a
> PLX9054-based PCI card. The 2.4.25-kernel on the 3.1.1 ELDK had big
> problems to map the PCI resources of this card, so I tried the latest
> 2.6.19.2-kernel of the 4.1 ELDK. This kernel mapped successfully the PCI
> resources on this card.
> After building the latest PLX driver on the 2.6.19-kernel (I had to make
> some changes for the .19 kernel and for some litte/big endian issues) I
> was able to transfer data with programmed I/O. But as this is too slow I
> like to use the DMA functions of this device and here is the problem:
> PLX provides an example program for scatter/gather DMA. This program
> works with their latetst driver on a linux PC. But on the TQM5200 the
> 'Channel 0 done' flag of the DMASR0 register is never set after starting
> the DMA transfer. What can be the reason for this? The debug output of
> the driver looks O.K., but waiting for the DMA done interrupt gives a
> timeout, because the flag is not set. I wrote some test patterns in my
> DMA buffer before the DMA transfer and no byte of the buffer was
> altered, so the DMA engine seems not to be able to write a single byte.
> Has anybody this or a similar card running on a ppc environment? Any
> ideas what I can do?
>
> Thanks in advance and bye,
Hi,
I use the PLX-9054 in my custom boards (TI DSP on-board), and
Linux x86 host computer. When debugging, I load a simple memmap
driver, and 'tickle' the board registers directly.
There's a copy of the PLX driver in here ...
http://www.ovro.caltech.edu/~dwh/correlator/pdf/cobra_driver.pdf
http://www.ovro.caltech.edu/~dwh/correlator/software/cobra_driver-2.9.tar.gz
And if my memory serves me right, I think I wrote a generic
one that lets you map any PCI device ...
http://www.ovro.caltech.edu/~dwh/correlator/pdf/LNX-723-Hawkins.pdf
http://www.ovro.caltech.edu/~dwh/correlator/software/driver_design.tar.gz
Anyway, manually setup a DMA transfer and convince yourself that
you know which bits to twiddle, then figure out why the driver
code isn't doing as its asked.
Take a look at the COBRA driver code, it has PLX-9054 DMA control.
There might be a few clues in my docs that'll help you.
Cheers
Dave
next prev parent reply other threads:[~2007-03-01 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 12:44 MPC5200, PLX9054 PCI Card - stalled DMA transfers Oliver Rutsch
2007-03-01 22:48 ` David Hawkins [this message]
2007-03-08 7:47 ` Oliver Rutsch
2007-03-08 12:20 ` Sylvain Munaut
2007-03-09 17:03 ` David Hawkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45E75859.3090508@ovro.caltech.edu \
--to=dwh@ovro$(echo .)caltech.edu \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=orutsch@sympatec$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox