This is a note to let you know that I've just added the patch titled

    drm/radeon: activate UVD clocks before sending the destroy msg

to the 3.12-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     drm-radeon-activate-uvd-clocks-before-sending-the-destroy-msg.patch
and it can be found in the queue-3.12 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From c154a76311293f9671439286834aa325b7ef59fe Mon Sep 17 00:00:00 2001
From: Christian König <[email protected]>
Date: Wed, 30 Oct 2013 12:56:04 +0100
Subject: drm/radeon: activate UVD clocks before sending the destroy msg

From: Christian König <[email protected]>

commit c154a76311293f9671439286834aa325b7ef59fe upstream.

Make sure the UVD clocks are still active before sending
the destroy message, otherwise the hw might hang.

Signed-off-by: Christian König <[email protected]>
Signed-off-by: Alex Deucher <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 drivers/gpu/drm/radeon/radeon_uvd.c |    2 ++
 1 file changed, 2 insertions(+)

--- a/drivers/gpu/drm/radeon/radeon_uvd.c
+++ b/drivers/gpu/drm/radeon/radeon_uvd.c
@@ -240,6 +240,8 @@ void radeon_uvd_free_handles(struct rade
                if (handle != 0 && rdev->uvd.filp[i] == filp) {
                        struct radeon_fence *fence;
 
+                       radeon_uvd_note_usage(rdev);
+
                        r = radeon_uvd_get_destroy_msg(rdev,
                                R600_RING_TYPE_UVD_INDEX, handle, &fence);
                        if (r) {


Patches currently in stable-queue which might be from [email protected] 
are

queue-3.12/drm-radeon-fix-uvd-destroy-ib-size.patch
queue-3.12/drm-radeon-activate-uvd-clocks-before-sending-the-destroy-msg.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to