linux_dsm_epyc7002/kernel/dma
Christoph Hellwig 4268ac6ae5 dma-direct: don't check swiotlb=force in dma_direct_map_resource
When mapping resources we can't just use swiotlb ram for bounce
buffering.  Switch to a direct dma_capable check instead.

Fixes: cfced78696 ("dma-mapping: remove the default map_resource implementation")
Reported-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>
Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
2019-11-20 20:31:41 +01:00
..
coherent.c dma-mapping: fix handling of dma-ranges for reserved memory (again) 2019-10-30 11:07:35 -07:00
contiguous.c kernel: dma-contiguous: mark CMA parameters __initdata/__initconst 2019-10-30 11:10:45 -07:00
debug.c dma-debug: clean up put_hash_bucket() 2019-11-20 20:31:41 +01:00
direct.c dma-direct: don't check swiotlb=force in dma_direct_map_resource 2019-11-20 20:31:41 +01:00
dummy.c dma-mapping: factor out dummy DMA ops 2018-12-13 21:06:12 +01:00
Kconfig dma-direct: provide mmap and get_sgtable method overrides 2019-11-11 10:52:15 +01:00
Makefile dma-mapping: improve selection of dma_declare_coherent availability 2019-02-20 07:26:35 -07:00
mapping.c dma-direct: provide mmap and get_sgtable method overrides 2019-11-11 10:52:15 +01:00
remap.c dma-mapping: merge the generic remapping helpers into dma-direct 2019-11-11 10:52:18 +01:00
swiotlb.c powerpc updates for 5.4 2019-09-20 11:48:06 -07:00
virt.c dma-mapping: zero memory returned from dma_alloc_* 2018-12-20 08:13:52 +01:00