linux/kernel/dma
Christoph Hellwig e15db62bc5 swiotlb: fix setting ->force_bounce
The swiotlb_init refactor messed up assigning ->force_bounce by doing
it in different places based on what caused the setting of the flag.

Fix this by passing the SWIOTLB_* flags to swiotlb_init_io_tlb_mem
and just setting it there.

Fixes: c6af2aa9ff ("swiotlb: make the swiotlb_init interface more useful")
Reported-by: Nathan Chancellor <nathan@kernel.org>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Tested-by: Nathan Chancellor <nathan@kernel.org>
2022-06-02 07:17:59 +02:00
..
Kconfig
Makefile
coherent.c
contiguous.c
debug.c dma-debug: make things less spammy under memory pressure 2022-06-02 07:17:59 +02:00
debug.h
direct.c dma-direct: don't over-decrypt memory 2022-05-23 15:25:40 +02:00
direct.h dma-direct: use is_swiotlb_active in dma_direct_map_page 2022-04-18 07:21:08 +02:00
dummy.c
map_benchmark.c
mapping.c
ops_helpers.c
pool.c
remap.c
swiotlb.c swiotlb: fix setting ->force_bounce 2022-06-02 07:17:59 +02:00