aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm/include/asm
diff options
context:
space:
mode:
authorRussell King <rmk@dyn-67.arm.linux.org.uk>2008-09-29 14:50:59 -0400
committerRussell King <rmk+kernel@arm.linux.org.uk>2008-09-30 06:01:36 -0400
commit309dbbabee7b19e003e1ba4b98f43d28f390a84e (patch)
treeba748b84c0573f5eb151a581e333b95010576521 /arch/arm/include/asm
parent0e18b5d7c6339311f1e32e7b186ae3556c5b6d33 (diff)
[ARM] dma: don't touch cache on dma_*_for_cpu()
As per the dma_unmap_* calls, we don't touch the cache when a DMA buffer transitions from device to CPU ownership. Presently, no problems have been identified with speculative cache prefetching which in itself is a new feature in later architectures. We may have to revisit the DMA API later for these architectures anyway. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'arch/arm/include/asm')
-rw-r--r--arch/arm/include/asm/dma-mapping.h6
1 files changed, 1 insertions, 5 deletions
diff --git a/arch/arm/include/asm/dma-mapping.h b/arch/arm/include/asm/dma-mapping.h
index 2544a087c213..ad62020763f1 100644
--- a/arch/arm/include/asm/dma-mapping.h
+++ b/arch/arm/include/asm/dma-mapping.h
@@ -376,11 +376,7 @@ static inline void dma_sync_single_range_for_cpu(struct device *dev,
376{ 376{
377 BUG_ON(!valid_dma_direction(dir)); 377 BUG_ON(!valid_dma_direction(dir));
378 378
379 if (!dmabounce_sync_for_cpu(dev, handle, offset, size, dir)) 379 dmabounce_sync_for_cpu(dev, handle, offset, size, dir);
380 return;
381
382 if (!arch_is_coherent())
383 dma_cache_maint(dma_to_virt(dev, handle) + offset, size, dir);
384} 380}
385 381
386static inline void dma_sync_single_range_for_device(struct device *dev, 382static inline void dma_sync_single_range_for_device(struct device *dev,