drm/amdgpu: drop the extra fence range check v2

Amdgpu doesn't support using scratch registers for fences any more.
So we won't see values like 0xdeadbeef as fence value any more.

v2: reschedule timer even if no change detected

Signed-off-by: Christian König <christian.koenig@amd.com>
Acked-by: Alex Deucher <alexander.deucher@amd.com>
Reviewed-by: Chunming Zhou <david1.zhou@amd.com>

diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
index c5980c4133a62d9834a4845615caccc053670c89..fa4eabeee71d839645c054dc88551f02dbb928d6 100644 (file)
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
@@ -190,9 +190,6 @@ void amdgpu_fence_process(struct amdgpu_ring *ring)
                        seq |= last_emitted & 0xffffffff00000000LL;
                }
 
-               if (seq <= last_seq || seq > last_emitted)
-                       return;
-
        } while (atomic64_cmpxchg(&drv->last_seq, last_seq, seq) != last_seq);
 
        if (seq < last_emitted)