aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/radeon/evergreen.c
diff options
context:
space:
mode:
authorChristian König <christian.koenig@amd.com>2014-02-18 06:37:50 -0500
committerChristian König <christian.koenig@amd.com>2014-02-18 11:50:00 -0500
commit2d2fe3f9b60fd3cc9a19dcc3ae892a23825da07f (patch)
treec2bbdb57e1d33b271b84a1eb9463ad073f7c0f4a /drivers/gpu/drm/radeon/evergreen.c
parentff212f25feb44a915ce9c0144faef7fae27a6e61 (diff)
drm/radeon: drop radeon_ring_force_activity
The reason for the false positives was fixed quite some time ago and since most engines can still execute NOPs while being locked up it leads to false negatives. Signed-off-by: Christian König <christian.koenig@amd.com> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/radeon/evergreen.c')
-rw-r--r--drivers/gpu/drm/radeon/evergreen.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/gpu/drm/radeon/evergreen.c b/drivers/gpu/drm/radeon/evergreen.c
index d9156be5b9a6..c78d8ece9504 100644
--- a/drivers/gpu/drm/radeon/evergreen.c
+++ b/drivers/gpu/drm/radeon/evergreen.c
@@ -3953,8 +3953,6 @@ bool evergreen_gfx_is_lockup(struct radeon_device *rdev, struct radeon_ring *rin
3953 radeon_ring_lockup_update(rdev, ring); 3953 radeon_ring_lockup_update(rdev, ring);
3954 return false; 3954 return false;
3955 } 3955 }
3956 /* force CP activities */
3957 radeon_ring_force_activity(rdev, ring);
3958 return radeon_ring_test_lockup(rdev, ring); 3956 return radeon_ring_test_lockup(rdev, ring);
3959} 3957}
3960 3958