drm/tegra: Implement correct DMA-BUF semantics
DMA-BUF requires that each device that accesses a DMA-BUF attaches to it
separately. To do so the host1x_bo_pin() and host1x_bo_unpin() functions
need to be reimplemented so that they can return a mapping, which either
represents an attachment or a map of the driver's own GEM object.
Signed-off-by:
Thierry Reding <treding@nvidia.com>
Showing
- drivers/gpu/drm/tegra/gem.c 102 additions, 61 deletionsdrivers/gpu/drm/tegra/gem.c
- drivers/gpu/drm/tegra/plane.c 15 additions, 45 deletionsdrivers/gpu/drm/tegra/plane.c
- drivers/gpu/drm/tegra/plane.h 1 addition, 1 deletiondrivers/gpu/drm/tegra/plane.h
- drivers/gpu/drm/tegra/submit.c 45 additions, 17 deletionsdrivers/gpu/drm/tegra/submit.c
- drivers/gpu/drm/tegra/uapi.c 25 additions, 43 deletionsdrivers/gpu/drm/tegra/uapi.c
- drivers/gpu/drm/tegra/uapi.h 2 additions, 3 deletionsdrivers/gpu/drm/tegra/uapi.h
- drivers/gpu/host1x/job.c 57 additions, 103 deletionsdrivers/gpu/host1x/job.c
- drivers/gpu/host1x/job.h 1 addition, 5 deletionsdrivers/gpu/host1x/job.h
- include/linux/host1x.h 20 additions, 10 deletionsinclude/linux/host1x.h
Loading
Please register or sign in to comment