From: Josh Triplett <josh@joshtriplett.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Failing to get DMA working with MPC5200 (TQM5200) and CompactFlash
Date: Fri, 26 Mar 2010 14:32:02 -0700 [thread overview]
Message-ID: <20100326213202.GD5350@feather> (raw)
In-Reply-To: <fa686aa41003261122s7c03244bm2ffc3347263af613@mail.gmail.com>
On Fri, Mar 26, 2010 at 12:22:32PM -0600, Grant Likely wrote:
> On Tue, Mar 16, 2010 at 11:17 PM, Josh Triplett <josh@joshtriplett.org> wrote:
> > Hello,
> >
> > We've tried both 2.6.33 and DENX-v2.6.33.1, and we haven't managed to
> > successfully use any form of DMA with the TQM5200 and a CompactFlash
> > card. We know the CF card supports DMA (or, at least, it says "UDMA"
> > right on the card, and various reports say Lexar Professional CF cards
> > do DMA), but the kernel always puts the card in PIO4 mode. We tried
> > libata.force=mwdma2 and libata.force=udma2 , and many other modes, but
> > this always led to failures like this:
> >
> > [ 31.994311] ata1: lost interrupt (Status 0x58)
> > [ 32.020435] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> > [ 32.027712] ata1.00: failed command: READ DMA
> > [ 32.032236] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
> > [ 32.032249] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> > [ 32.047212] ata1.00: status: { DRDY }
> > [ 32.051050] ata1: soft resetting link
> > [ 32.218796] ata1.00: FORCE: xfer_mask set to udma2
> > [ 32.230618] ata1.00: configured for UDMA/33
> > [ 32.235000] ata1.00: device reported invalid CHS sector 0
> > [ 32.240629] ata1: EH complete
> > [ 62.994310] ata1: lost interrupt (Status 0x58)
> > [ 63.020443] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> > [ 63.027722] ata1.00: failed command: READ DMA
> > [ 63.032246] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
> > [ 63.032259] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> > [ 63.047221] ata1.00: status: { DRDY }
> > [ 63.051060] ata1: soft resetting link
> > [ 63.218778] ata1.00: FORCE: xfer_mask set to udma2
> > [ 63.238603] ata1.00: configured for UDMA/33
> > [ 63.242978] ata1.00: device reported invalid CHS sector 0
> > [ 63.248609] ata1: EH complete
> >
> > We have the MPC5200C revision of the silicon.
> >
> > Does this sound like a known issue? Can we do anything to troubleshoot
> > this further?
>
> Not all CF adapters have all the pins wired up that are needed for
> *DMA modes. That is the most likely problem.
True, but we bought a card that specifically advertises support for
UDMA, and says UDMA right on the card's label.
http://store.lexar.com/?productid=CF8GB-300-381
It seems unlikely, though not impossible, that they would have screwed
up that badly. :)
By the way, we've also tested an IDE hard drive on this board, and it
does UDMA2 just fine.
Any thoughts on how we could try to solve this problem?
- Josh Triplett
next prev parent reply other threads:[~2010-03-26 21:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 5:17 Failing to get DMA working with MPC5200 (TQM5200) and CompactFlash Josh Triplett
2010-03-26 18:22 ` Grant Likely
2010-03-26 21:32 ` Josh Triplett [this message]
2010-03-26 22:02 ` Grant Likely
2010-03-26 22:17 ` Wolfgang Wegner
2010-03-26 22:44 ` Grant Likely
2010-03-26 22:59 ` Josh Triplett
2010-03-27 13:22 ` Albrecht Dreß
2010-03-28 22:24 ` Josh Triplett
2010-03-29 18:42 ` Albrecht Dreß
2010-03-29 21:30 ` Josh Triplett
2010-03-27 17:44 ` Wolfgang Denk
2010-03-28 22:23 ` Josh Triplett
2010-03-30 0:09 ` Wolfram Sang
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=20100326213202.GD5350@feather \
--to=josh@joshtriplett.org \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.