linux

iv/linux

Files

Christoph Hellwig b8444fa88d dma-direct: don't check swiotlb=force in dma_direct_map_resource

[ Upstream commit 4268ac6ae5 ]

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>
Signed-off-by: Sasha Levin <sashal@kernel.org>

2020-01-26 10:01:08 +01:00

coherent.c

dma-mapping: fix handling of dma-ranges for reserved memory (again)

2020-01-04 19:17:00 +01:00

contiguous.c

dma-direct: fix zone selection after an unaddressable CMA allocation

2019-08-21 07:14:10 +09:00

debug.c

dma-debug: add a schedule point in debug_dma_dump_mappings()

2020-01-04 19:16:57 +01:00

direct.c

dma-direct: don't check swiotlb=force in dma_direct_map_resource