aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/lima/lima_gem.c
diff options
context:
space:
mode:
authorMarek Szyprowski <[email protected]>2020-05-08 06:26:50 +0000
committerMarek Szyprowski <[email protected]>2020-09-10 06:18:35 +0000
commite96418da0a2b9f52538c4a84f6f565708d7ed32e (patch)
treef3d266122517b5230b3ca07c1ab48f7a7de31daa /drivers/gpu/drm/lima/lima_gem.c
parentdrm: tegra: fix common struct sg_table related issues (diff)
downloadkernel-e96418da0a2b9f52538c4a84f6f565708d7ed32e.tar.gz
kernel-e96418da0a2b9f52538c4a84f6f565708d7ed32e.zip
drm: v3d: fix common struct sg_table related issues
The Documentation/DMA-API-HOWTO.txt states that the dma_map_sg() function returns the number of the created entries in the DMA address space. However the subsequent calls to the dma_sync_sg_for_{device,cpu}() and dma_unmap_sg must be called with the original number of the entries passed to the dma_map_sg(). struct sg_table is a common structure used for describing a non-contiguous memory buffer, used commonly in the DRM and graphics subsystems. It consists of a scatterlist with memory pages and DMA addresses (sgl entry), as well as the number of scatterlist entries: CPU pages (orig_nents entry) and DMA mapped pages (nents entry). It turned out that it was a common mistake to misuse nents and orig_nents entries, calling DMA-mapping functions with a wrong number of entries or ignoring the number of mapped entries returned by the dma_map_sg() function. To avoid such issues, lets use a common dma-mapping wrappers operating directly on the struct sg_table objects and use scatterlist page iterators where possible. This, almost always, hides references to the nents and orig_nents entries, making the code robust, easier to follow and copy/paste safe. Signed-off-by: Marek Szyprowski <[email protected]> Reviewed-by: Eric Anholt <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/lima/lima_gem.c')
0 files changed, 0 insertions, 0 deletions