Christoph Hellwig a4a4330db4 swiotlb: add support for non-coherent DMA ... Handle architectures that are not cache coherent directly in the main swiotlb code by calling arch_sync_dma_for_{device,cpu} in all the right places from the various dma_map/unmap/sync methods when the device is non-coherent. Because swiotlb now uses dma_direct_alloc for the coherent allocation that side is already taken care of by the dma-direct code calling into arch_dma_{alloc,free} for devices that are non-coherent. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>		2018-10-19 08:53:05 +02:00
..
coherent.c	dma-mapping: move all DMA mapping code to kernel/dma	2018-06-14 08:50:37 +02:00
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-debug: Check for drivers mapping invalid addresses in dma_map_single()	2018-10-08 09:44:17 +02:00
direct.c	swiotlb: remove the overflow buffer	2018-10-19 08:43:46 +02:00
Kconfig	dma-mapping: consolidate the dma mmap implementations	2018-09-20 09:01:16 +02:00
Makefile	dma-mapping: merge direct and noncoherent ops	2018-09-20 09:01:15 +02:00
mapping.c	dma-mapping: support non-coherent devices in dma_common_get_sgtable	2018-09-20 09:01:17 +02:00
swiotlb.c	swiotlb: add support for non-coherent DMA	2018-10-19 08:53:05 +02:00
virt.c	dma-mapping: move all DMA mapping code to kernel/dma	2018-06-14 08:50:37 +02:00