summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/radeon/radeon_object.c
diff options
context:
space:
mode:
authorChristian König <christian.koenig@amd.com>2014-07-30 21:04:55 +0200
committerAlex Deucher <alexander.deucher@amd.com>2014-08-05 08:53:53 -0400
commite7e31600d3e2f8b7726b0521149fc55c62a90467 (patch)
treedeb9ed61fe5b5b583b8b065b34c643a7c9511815 /drivers/gpu/drm/radeon/radeon_object.c
parentdfc230f9aff93cc67faf7e0e191dbb3dd7c6ecbb (diff)
downloadop-kernel-dev-e7e31600d3e2f8b7726b0521149fc55c62a90467.zip
op-kernel-dev-e7e31600d3e2f8b7726b0521149fc55c62a90467.tar.gz
drm/radeon: remove taking mclk_lock from radeon_bo_unref
It's causing lockdep warnings and why should we access the memory that is freed up? Signed-off-by: Christian König <christian.koenig@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/radeon/radeon_object.c')
-rw-r--r--drivers/gpu/drm/radeon/radeon_object.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/gpu/drm/radeon/radeon_object.c b/drivers/gpu/drm/radeon/radeon_object.c
index 78b74c8..9505766 100644
--- a/drivers/gpu/drm/radeon/radeon_object.c
+++ b/drivers/gpu/drm/radeon/radeon_object.c
@@ -245,9 +245,7 @@ void radeon_bo_unref(struct radeon_bo **bo)
return;
rdev = (*bo)->rdev;
tbo = &((*bo)->tbo);
- down_read(&rdev->pm.mclk_lock);
ttm_bo_unref(&tbo);
- up_read(&rdev->pm.mclk_lock);
if (tbo == NULL)
*bo = NULL;
}
OpenPOWER on IntegriCloud