This is a note to let you know that I've just added the patch titled
drm/radeon: add missing crtc unlock when setting up the MC
to the 3.17-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-add-missing-crtc-unlock-when-setting-up-the-mc.patch
and it can be found in the queue-3.17 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From f0d7bfb9407fccb6499ec01c33afe43512a439a2 Mon Sep 17 00:00:00 2001
From: Alex Deucher <alexander.deucher@xxxxxxx>
Date: Wed, 5 Nov 2014 17:14:32 -0500
Subject: drm/radeon: add missing crtc unlock when setting up the MC
From: Alex Deucher <alexander.deucher@xxxxxxx>
commit f0d7bfb9407fccb6499ec01c33afe43512a439a2 upstream.
Need to unlock the crtc after updating the blanking state.
Signed-off-by: Alex Deucher <alexander.deucher@xxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/gpu/drm/radeon/evergreen.c | 1 +
1 file changed, 1 insertion(+)
--- a/drivers/gpu/drm/radeon/evergreen.c
+++ b/drivers/gpu/drm/radeon/evergreen.c
@@ -2556,6 +2556,7 @@ void evergreen_mc_stop(struct radeon_dev
WREG32(EVERGREEN_CRTC_UPDATE_LOCK + crtc_offsets[i], 1);
tmp |= EVERGREEN_CRTC_BLANK_DATA_EN;
WREG32(EVERGREEN_CRTC_BLANK_CONTROL + crtc_offsets[i], tmp);
+ WREG32(EVERGREEN_CRTC_UPDATE_LOCK + crtc_offsets[i], 0);
}
} else {
tmp = RREG32(EVERGREEN_CRTC_CONTROL + crtc_offsets[i]);
Patches currently in stable-queue which might be from alexander.deucher@xxxxxxx are
queue-3.17/drm-radeon-make-sure-mode-init-is-complete-in-bandwidth_update.patch
queue-3.17/drm-radeon-add-missing-crtc-unlock-when-setting-up-the-mc.patch
queue-3.17/drm-radeon-add-locking-around-atombios-scratch-space-usage.patch
queue-3.17/drm-radeon-use-gart-for-dma-ib-tests.patch
queue-3.17/drm-radeon-set-correct-ce-ram-size-for-cik.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html