summaryrefslogtreecommitdiffstats
path: root/arch/microblaze
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2019-08-06 14:06:40 +0200
committerChristoph Hellwig <hch@lst.de>2019-09-04 11:13:18 +0200
commit62fcee9a3bd73e279d3052245a652a918d0c51da (patch)
treef1beed23ef1bbebfa0b3a9b0c3439feb5b710413 /arch/microblaze
parentparisc: don't set ARCH_NO_COHERENT_DMA_MMAP (diff)
downloadlinux-62fcee9a3bd73e279d3052245a652a918d0c51da.tar.xz
linux-62fcee9a3bd73e279d3052245a652a918d0c51da.zip
dma-mapping: remove CONFIG_ARCH_NO_COHERENT_DMA_MMAP
CONFIG_ARCH_NO_COHERENT_DMA_MMAP is now functionally identical to !CONFIG_MMU, so remove the separate symbol. The only difference is that arm did not set it for !CONFIG_MMU, but arm uses a separate dma mapping implementation including its own mmap method, which is handled by moving the CONFIG_MMU check in dma_can_mmap so that is only applies to the dma-direct case, just as the other ifdefs for it. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org> # m68k
Diffstat (limited to 'arch/microblaze')
-rw-r--r--arch/microblaze/Kconfig1
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/microblaze/Kconfig b/arch/microblaze/Kconfig
index d411de05b628..632c9477a0f6 100644
--- a/arch/microblaze/Kconfig
+++ b/arch/microblaze/Kconfig
@@ -9,7 +9,6 @@ config MICROBLAZE
select ARCH_HAS_SYNC_DMA_FOR_CPU
select ARCH_HAS_SYNC_DMA_FOR_DEVICE
select ARCH_MIGHT_HAVE_PC_PARPORT
- select ARCH_NO_COHERENT_DMA_MMAP if !MMU
select ARCH_WANT_IPC_PARSE_VERSION
select BUILDTIME_EXTABLE_SORT
select TIMER_OF