DMA/cache problems on SA1110/SA1111 (Was: Re: USB Host on a SA1111)
Russell King - ARM Linux
linux at arm.linux.org.uk
Tue Dec 22 11:59:04 EST 2009
On Tue, Dec 22, 2009 at 05:33:30PM +0100, Filip Zyzniewski wrote:
> On Thu, Dec 17, 2009 at 10:13 PM, Russell King - ARM Linux
> <linux at arm.linux.org.uk> wrote:
> >> Russell you got any clues on this? From my point of view it really should
> >> just work. But Ive never done this myself.
> > I've never really been that much involved with USB stuff, so can't really
> > comment.
> There was some discussion about this at linux-usb mailing list.
> The interesting part is here:
> Especially the last post by Alan Stern:
> > I looked at one of these logs. Apparently there's a problem with the
> > memory caching and DMA. With some of the commands, the debugging
> > message shows incorrect data in the buffer. But later on, when the
> > data gets used, it obviously is correct.
> > This implies that something is wrong with the implementation of
> > dma_map_single() or dma_unmap_unsingle(). And it might explain why
> > changing the system's cache settings affects the behavior.
> I don't know architecture handling details, could somebody more
> knowledgeable give me
> some clues about where to begin fixing this? What could be broken?
Make sure that the DMA mask is correctly set - SA1111's have a bug in them
which means that certain address bits must have a certain value for all
We set the DMA masks up properly for the devices in the SA1111 core code,
and rely on the DMA bounce hack to bounce any unsatisfactory buffers into
regions of memory which should avoid the hardware bug.
This also relies upon having the system memory described properly to the
kernel - which basically means ensuring that GFP_DMA returns memory which
can be DMA'd by _any_ device in the system.
Assabet with Neponset should be a good place to look at - I thought at
least the memory layout was all done automatically by the kernel if
SA1111 support was enabled.
More information about the linux-arm-kernel