Christoph Hellwig 55897af630 dma-direct: merge swiotlb_dma_ops into the dma_direct code ... While the dma-direct code is (relatively) clean and simple we actually have to use the swiotlb ops for the mapping on many architectures due to devices with addressing limits. Instead of keeping two implementations around this commit allows the dma-direct implementation to call the swiotlb bounce buffering functions and thus share the guts of the mapping implementation. This also simplified the dma-mapping setup on a few architectures where we don't have to differenciate which implementation to use. 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>		2018-12-13 21:06:17 +01:00
..
coherent.c
contiguous.c	dma-mapping: fix panic caused by passing empty cma command line argument	2018-09-20 09:01:08 +02:00
debug.c	dma-mapping: simplify the dma_sync_single_range_for_{cpu,device} implementation	2018-12-13 21:06:08 +01:00
direct.c	dma-direct: merge swiotlb_dma_ops into the dma_direct code	2018-12-13 21:06:17 +01:00
dummy.c	dma-mapping: factor out dummy DMA ops	2018-12-13 21:06:12 +01:00
Kconfig	dma-mapping: always build the direct mapping code	2018-12-13 21:06:11 +01:00
Makefile	dma-mapping: factor out dummy DMA ops	2018-12-13 21:06:12 +01:00
mapping.c	dma-mapping: move dma_cache_sync out of line	2018-12-13 21:06:10 +01:00
remap.c	dma-mapping: remove a pointless memset in dma_atomic_pool_init	2018-12-13 21:05:20 +01:00
swiotlb.c	dma-direct: merge swiotlb_dma_ops into the dma_direct code	2018-12-13 21:06:17 +01:00
virt.c