Searched hist:c6aeaf56f468a565f6d2f27325fc07d35cdcd3cb (Results 1 – 9 of 9) sorted by relevance
| /openbmc/linux/drivers/gpu/drm/tegra/ |
| H A D | uapi.h | diff c6aeaf56f468a565f6d2f27325fc07d35cdcd3cb Thu Sep 09 08:51:24 CDT 2021 Thierry Reding <treding@nvidia.com> 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>
|
| H A D | submit.c | diff c6aeaf56f468a565f6d2f27325fc07d35cdcd3cb Thu Sep 09 08:51:24 CDT 2021 Thierry Reding <treding@nvidia.com> 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>
|
| H A D | uapi.c | diff c6aeaf56f468a565f6d2f27325fc07d35cdcd3cb Thu Sep 09 08:51:24 CDT 2021 Thierry Reding <treding@nvidia.com> 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>
|
| H A D | plane.h | diff c6aeaf56f468a565f6d2f27325fc07d35cdcd3cb Thu Sep 09 08:51:24 CDT 2021 Thierry Reding <treding@nvidia.com> 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>
|
| H A D | plane.c | diff c6aeaf56f468a565f6d2f27325fc07d35cdcd3cb Thu Sep 09 08:51:24 CDT 2021 Thierry Reding <treding@nvidia.com> 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>
|
| H A D | gem.c | diff c6aeaf56f468a565f6d2f27325fc07d35cdcd3cb Thu Sep 09 08:51:24 CDT 2021 Thierry Reding <treding@nvidia.com> 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>
|
| /openbmc/linux/drivers/gpu/host1x/ |
| H A D | job.h | diff c6aeaf56f468a565f6d2f27325fc07d35cdcd3cb Thu Sep 09 08:51:24 CDT 2021 Thierry Reding <treding@nvidia.com> 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>
|
| H A D | job.c | diff c6aeaf56f468a565f6d2f27325fc07d35cdcd3cb Thu Sep 09 08:51:24 CDT 2021 Thierry Reding <treding@nvidia.com> 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>
|
| /openbmc/linux/include/linux/ |
| H A D | host1x.h | diff c6aeaf56f468a565f6d2f27325fc07d35cdcd3cb Thu Sep 09 08:51:24 CDT 2021 Thierry Reding <treding@nvidia.com> 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>
|