Workaround for USB DMA bugs
dan at embeddededge.com
Thu Apr 4 03:49:53 EST 2002
> Ah yes, We have done something simular (internally) and had the same
> reservations. This will help me with the ocp usb drivers i am working
> on. I would like to see some way of reminding us that this was done.
> let say a config option for 4xx_usb_dma_workarround.
It isn't unique to 4xx. This was originally done for the 8xx USB (actually,
probably for StrongARM and I just copied it over). These functions are
only used for incoherent processors, so there isn't any need to further
define this with another config option. Just leave a comment here, change
the #ifdef CONFIG_USB to #if 1 (it should be done all of the time).
Just remember this is not a solution, and simply makes the problem less
likely to appear. If you happen to perform this operation, and then the
processor happens to touch the cache line before the DMA is complete,
your DMA buffer will still be corrputed. So far, we have just been lucky
the DMA completes before anything else in the cache line is touched by
the processor. This only guarantees the processor will never get incorrect
information when it shares a cache line with a DMA.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-embedded