提交 2e536084 编写于 作者: M monk.liu 提交者: Alex Deucher

drm/amdgpu: use kernel fence interface when possible

Signed-off-by: Nmonk.liu <monk.liu@amd.com>
Reviewed-by: NChristian König <christian.koenig@amd.com>
上级 8128765c
...@@ -622,18 +622,11 @@ static long amdgpu_fence_wait_seq_timeout(struct amdgpu_device *adev, ...@@ -622,18 +622,11 @@ static long amdgpu_fence_wait_seq_timeout(struct amdgpu_device *adev,
*/ */
int amdgpu_fence_wait(struct amdgpu_fence *fence, bool intr) int amdgpu_fence_wait(struct amdgpu_fence *fence, bool intr)
{ {
uint64_t seq[AMDGPU_MAX_RINGS] = {};
long r; long r;
seq[fence->ring->idx] = fence->seq; r = fence_wait_timeout(&fence->base, intr, MAX_SCHEDULE_TIMEOUT);
r = amdgpu_fence_wait_seq_timeout(fence->ring->adev, seq, intr, MAX_SCHEDULE_TIMEOUT); if (r < 0)
if (r < 0) { return r;
return r;
}
r = fence_signal(&fence->base);
if (!r)
FENCE_TRACE(&fence->base, "signaled from fence_wait\n");
return 0; return 0;
} }
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册