Christoph Hellwig a5008b59cd dma-direct: only limit the mapping size if swiotlb could be used ... Don't just check for a swiotlb buffer, but also if buffering might be required for this particular device. Fixes: 133d624b1c ("dma: Introduce dma_max_mapping_size()") Reported-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Christoph Hellwig <hch@lst.de> Tested-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>		2019-07-17 08:25:45 +02:00
..
coherent.c	dma-mapping: remove the DMA_MEMORY_EXCLUSIVE flag	2019-02-20 07:27:00 -07:00
contiguous.c	dma-contiguous: use fallback alloc_pages for single pages	2019-06-03 16:00:07 +02:00
debug.c	treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 333	2019-06-05 17:37:06 +02:00
direct.c	dma-direct: only limit the mapping size if swiotlb could be used	2019-07-17 08:25:45 +02:00
dummy.c	dma-mapping: factor out dummy DMA ops	2018-12-13 21:06:12 +01:00
Kconfig	dma-direct: Force unencrypted DMA under SME for certain DMA masks	2019-07-16 22:15:46 +02:00
Makefile	dma-mapping: improve selection of dma_declare_coherent availability	2019-02-20 07:26:35 -07:00
mapping.c	dma-mapping: truncate dma masks to what dma_addr_t can hold	2019-06-25 07:54:06 +02:00
remap.c	dma-direct: handle DMA_ATTR_NO_KERNEL_MAPPING in common code	2019-06-25 14:28:05 +02:00
swiotlb.c	swiotlb: no need to check return value of debugfs_create functions	2019-07-03 16:57:18 +02:00
virt.c	dma-mapping: zero memory returned from dma_alloc_*	2018-12-20 08:13:52 +01:00