diff options
| author | Russell King <rmk@dyn-67.arm.linux.org.uk> | 2008-09-25 23:16:22 +0200 |
|---|---|---|
| committer | Russell King <rmk+kernel@arm.linux.org.uk> | 2008-09-29 11:40:22 +0200 |
| commit | 125ab12acf64ff86b55d20e14db20becd917b7c4 (patch) | |
| tree | ce39f81e6a3a409314735ce0cca1e366ea8fd94e /drivers | |
| parent | [ARM] dma: use new dmabounce_sync_for_xxx() for dma_sync_single_xxx() (diff) | |
| download | linux-125ab12acf64ff86b55d20e14db20becd917b7c4.tar.xz linux-125ab12acf64ff86b55d20e14db20becd917b7c4.zip | |
[ARM] dma: fix dmabounce dma_sync_xxx() implementations
The dmabounce dma_sync_xxx() implementation have been broken for
quite some time; they all copy data between the DMA buffer and
the CPU visible buffer no irrespective of the change of ownership.
(IOW, a DMA_FROM_DEVICE mapping copies data from the DMA buffer
to the CPU buffer during a call to dma_sync_single_for_device().)
Fix it by getting rid of sync_single(), moving the contents into
the recently created dmabounce_sync_for_xxx() functions and adjusting
appropriately.
This also makes it possible to properly support the DMA range sync
functions.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions