summaryrefslogtreecommitdiff
path: root/kernel/dma/Kconfig
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2018-12-06 23:50:26 +0300
committerChristoph Hellwig <hch@lst.de>2018-12-13 23:06:11 +0300
commit3731c3d4774e38b9d91c01943e1e6a243c1776be (patch)
tree5fda6811e4e89f40688493e3081f01e52216e6a7 /kernel/dma/Kconfig
parent8ddbe5943c0b1259b5ddb6dc1729863433fc256c (diff)
downloadlinux-3731c3d4774e38b9d91c01943e1e6a243c1776be.tar.xz
dma-mapping: always build the direct mapping code
All architectures except for sparc64 use the dma-direct code in some form, and even for sparc64 we had the discussion of a direct mapping mode a while ago. In preparation for directly calling the direct mapping code don't bother having it optionally but always build the code in. This is a minor hardship for some powerpc and arm configs that don't pull it in yet (although they should in a relase ot two), and sparc64 which currently doesn't need it at all, but it will reduce the ifdef mess we'd otherwise need significantly. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Jesper Dangaard Brouer <brouer@redhat.com> Tested-by: Jesper Dangaard Brouer <brouer@redhat.com> Tested-by: Tony Luck <tony.luck@intel.com>
Diffstat (limited to 'kernel/dma/Kconfig')
-rw-r--r--kernel/dma/Kconfig7
1 files changed, 0 insertions, 7 deletions
diff --git a/kernel/dma/Kconfig b/kernel/dma/Kconfig
index 41c3b1df70eb..ca88b867e7fe 100644
--- a/kernel/dma/Kconfig
+++ b/kernel/dma/Kconfig
@@ -35,13 +35,8 @@ config ARCH_HAS_DMA_COHERENT_TO_PFN
config ARCH_HAS_DMA_MMAP_PGPROT
bool
-config DMA_DIRECT_OPS
- bool
- depends on HAS_DMA
-
config DMA_NONCOHERENT_CACHE_SYNC
bool
- depends on DMA_DIRECT_OPS
config DMA_VIRT_OPS
bool
@@ -49,7 +44,6 @@ config DMA_VIRT_OPS
config SWIOTLB
bool
- select DMA_DIRECT_OPS
select NEED_DMA_MAP_STATE
config DMA_REMAP
@@ -58,5 +52,4 @@ config DMA_REMAP
config DMA_DIRECT_REMAP
bool
- depends on DMA_DIRECT_OPS
select DMA_REMAP