diff options
author | Christian König <christian.koenig@amd.com> | 2014-07-30 23:04:55 +0400 |
---|---|---|
committer | Alex Deucher <alexander.deucher@amd.com> | 2014-08-05 16:53:53 +0400 |
commit | e7e31600d3e2f8b7726b0521149fc55c62a90467 (patch) | |
tree | deb9ed61fe5b5b583b8b065b34c643a7c9511815 | |
parent | dfc230f9aff93cc67faf7e0e191dbb3dd7c6ecbb (diff) | |
download | linux-e7e31600d3e2f8b7726b0521149fc55c62a90467.tar.xz |
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>
-rw-r--r-- | drivers/gpu/drm/radeon/radeon_object.c | 2 |
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 78b74c88d145..9505766e46dd 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; } |