diff options
author | Ahmad Fatoum <ahmad@a3f.at> | 2021-04-16 08:24:33 +0200 |
---|---|---|
committer | Sascha Hauer <s.hauer@pengutronix.de> | 2021-05-03 14:06:30 +0200 |
commit | ce65ca49fda3a849f80ddb7d8cafcf90ed765e2c (patch) | |
tree | e569d8a0d856fab1a465a56748e00c27bfabb000 /arch/mips | |
parent | 02b7eaf6ab6b7c5c5f83b8742f3e43991e4cff1d (diff) | |
download | barebox-ce65ca49fda3a849f80ddb7d8cafcf90ed765e2c.tar.gz barebox-ce65ca49fda3a849f80ddb7d8cafcf90ed765e2c.tar.xz |
x86: add DMA support
Both interconnect and PCI are cache coherent on x86, so we shouldn't
need any special CPU barriers for DMA. Indeed, Linux defined neither
ARCH_HAS_SYNC_DMA_FOR_CPU nor ARCH_HAS_SYNC_DMA_FOR_DEVICE on x86.
It thus seems that the only reordering we need to take care of is
compiler-induced reordering. The Linux memory model that barebox adheres
to as well demands that all accesses to shared data are volatile.
volatile accesses are already guarnateed to not be reordered against
each other, so we don't even need an explicit barrier(), which is
already the case on other architectures that have a disabled MMU.
Cc: Lucas Stach <l.stach@pengutronix.de>
Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
Link: https://lore.barebox.org/20210416062436.332665-2-ahmad@a3f.at
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'arch/mips')
0 files changed, 0 insertions, 0 deletions