diff options
| author | Gurchetan Singh <gurchetansingh@chromium.org> | 2021-09-22 01:20:19 +0200 |
|---|---|---|
| committer | Gerd Hoffmann <kraxel@redhat.com> | 2021-09-29 09:22:30 +0200 |
| commit | e8b6e76f69a4336076a2e639d211c4cf3447ce87 (patch) | |
| tree | 9e58e2e80538b045cc86e39fb1869f55a9dd9442 /drivers/reset/reset-bcm6345.c | |
| parent | drm/virtio: implement context init: track {ring_idx, emit_fence_info} in virt... (diff) | |
| download | linux-e8b6e76f69a4336076a2e639d211c4cf3447ce87.tar.xz linux-e8b6e76f69a4336076a2e639d211c4cf3447ce87.zip | |
drm/virtio: implement context init: plumb {base_fence_ctx, ring_idx} to virtio_gpu_fence_alloc
These were defined in the previous commit. We'll need these
parameters when allocating a dma_fence. The use case for this
is multiple synchronizations timelines.
The maximum number of timelines per 3D instance will be 32. Usually,
only 2 are needed -- one for CPU commands, and another for GPU
commands.
As such, we'll need to specify these parameters when allocating a
dma_fence.
vgdev->fence_drv.context is the "default" fence context for 2D mode
and old userspace.
Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org>
Acked-by: Lingfeng Yang <lfy@google.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20210921232024.817-8-gurchetansingh@chromium.org
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'drivers/reset/reset-bcm6345.c')
0 files changed, 0 insertions, 0 deletions