diff options
author | Catalin Marinas <catalin.marinas@arm.com> | 2010-07-28 22:01:55 +0100 |
---|---|---|
committer | Russell King <rmk+kernel@arm.linux.org.uk> | 2010-07-29 14:04:37 +0100 |
commit | 79f64dbf68c8a9779a7e9a25e0a9f0217a25b57a (patch) | |
tree | bd75d76d566c5dd211d310bf136cf3e4b07184ae /COPYING | |
parent | 6775a558fece413376e1dacd435adb5fbe225f40 (diff) | |
download | linux-79f64dbf68c8a9779a7e9a25e0a9f0217a25b57a.tar.gz linux-79f64dbf68c8a9779a7e9a25e0a9f0217a25b57a.tar.bz2 linux-79f64dbf68c8a9779a7e9a25e0a9f0217a25b57a.zip |
ARM: 6273/1: Add barriers to the I/O accessors if ARM_DMA_MEM_BUFFERABLE
When the coherent DMA buffers are mapped as Normal Non-cacheable
(ARM_DMA_MEM_BUFFERABLE enabled), buffer accesses are no longer ordered
with Device memory accesses causing failures in device drivers that do
not use the mandatory memory barriers before starting a DMA transfer.
LKML discussions led to the conclusion that such barriers have to be
added to the I/O accessors:
http://thread.gmane.org/gmane.linux.kernel/683509/focus=686153
http://thread.gmane.org/gmane.linux.ide/46414
http://thread.gmane.org/gmane.linux.kernel.cross-arch/5250
This patch introduces a wmb() barrier to the write*() I/O accessors to
handle the situations where Normal Non-cacheable writes are still in the
processor (or L2 cache controller) write buffer before a DMA transfer
command is issued. For the read*() accessors, a rmb() is introduced
after the I/O to avoid speculative loads where the driver polls for a
DMA transfer ready bit.
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions