drm/vc4: Use newer fence API properly to fix build errors
The commit73511edf8b
("dma-buf: specify usage while adding fences to dma_resv obj v7") ported all the DRM drivers to use the newer fence API that specifies the usage with the enum dma_resv_usage rather than doing an explicit shared / exclusive distinction. But the commit didn't do it properly in two callers of the vc4 driver, leading to build errors. Fixes:73511edf8b
("dma-buf: specify usage while adding fences to dma_resv obj v7") Signed-off-by: Javier Martinez Canillas <javierm@redhat.com> Reviewed-by: Christian König <christian.koenig@amd.com> Link: https://patchwork.freedesktop.org/patch/msgid/20220407131950.915091-1-javierm@redhat.com
This commit is contained in:
parent
7cee157b42
commit
be273ecfbe
@ -546,7 +546,8 @@ vc4_update_bo_seqnos(struct vc4_exec_info *exec, uint64_t seqno)
|
||||
bo = to_vc4_bo(&exec->bo[i]->base);
|
||||
bo->seqno = seqno;
|
||||
|
||||
dma_resv_add_fence(bo->base.base.resv, exec->fence);
|
||||
dma_resv_add_fence(bo->base.base.resv, exec->fence,
|
||||
DMA_RESV_USAGE_READ);
|
||||
}
|
||||
|
||||
list_for_each_entry(bo, &exec->unref_list, unref_head) {
|
||||
@ -557,7 +558,8 @@ vc4_update_bo_seqnos(struct vc4_exec_info *exec, uint64_t seqno)
|
||||
bo = to_vc4_bo(&exec->rcl_write_bo[i]->base);
|
||||
bo->write_seqno = seqno;
|
||||
|
||||
dma_resv_add_excl_fence(bo->base.base.resv, exec->fence);
|
||||
dma_resv_add_fence(bo->base.base.resv, exec->fence,
|
||||
DMA_RESV_USAGE_WRITE);
|
||||
}
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user