aboutsummaryrefslogtreecommitdiff
path: root/lib/dma-direct.c
diff options
context:
space:
mode:
authorGravatar Robin Murphy <robin.murphy@arm.com> 2018-05-21 12:35:13 +0100
committerGravatar Christoph Hellwig <hch@lst.de> 2018-05-24 09:24:17 +0200
commit78c47830a5cbb5d22dc91819a95af3d5c4bec084 (patch)
tree43665ea5d3d05e734ea6a1399e7e5fdfd06b7792 /lib/dma-direct.c
parentc6x: use generic dma_noncoherent_ops (diff)
downloadlinux-78c47830a5cbb5d22dc91819a95af3d5c4bec084.tar.gz
linux-78c47830a5cbb5d22dc91819a95af3d5c4bec084.tar.bz2
linux-78c47830a5cbb5d22dc91819a95af3d5c4bec084.zip
dma-debug: check scatterlist segments
Drivers/subsystems creating scatterlists for DMA should be taking care to respect the scatter-gather limitations of the appropriate device, as described by dma_parms. A DMA API implementation cannot feasibly split a scatterlist into *more* entries than originally passed, so it is not well defined what they should do when given a segment larger than the limit they are also required to respect. Conversely, devices which are less limited than the rather conservative defaults, or indeed have no limitations at all (e.g. GPUs with their own internal MMU), should be encouraged to set appropriate dma_parms, as they may get more efficient DMA mapping performance out of it. Signed-off-by: Robin Murphy <robin.murphy@arm.com> Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'lib/dma-direct.c')
0 files changed, 0 insertions, 0 deletions