diff options
author | Christoph Hellwig <hch@lst.de> | 2018-12-06 23:50:26 +0300 |
---|---|---|
committer | Christoph Hellwig <hch@lst.de> | 2018-12-13 23:06:11 +0300 |
commit | 3731c3d4774e38b9d91c01943e1e6a243c1776be (patch) | |
tree | 5fda6811e4e89f40688493e3081f01e52216e6a7 /arch/microblaze | |
parent | 8ddbe5943c0b1259b5ddb6dc1729863433fc256c (diff) | |
download | linux-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 'arch/microblaze')
-rw-r--r-- | arch/microblaze/Kconfig | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/microblaze/Kconfig b/arch/microblaze/Kconfig index effed2efd306..eda9e2315ef5 100644 --- a/arch/microblaze/Kconfig +++ b/arch/microblaze/Kconfig @@ -12,7 +12,6 @@ config MICROBLAZE select TIMER_OF select CLONE_BACKWARDS3 select COMMON_CLK - select DMA_DIRECT_OPS select GENERIC_ATOMIC64 select GENERIC_CLOCKEVENTS select GENERIC_CPU_DEVICES |