This is a note to let you know that I've just added the patch titled
drm/radeon: don't share PPLLs on DCE4.1
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-don-t-share-pplls-on-dce4.1.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 <stable@xxxxxxxxxxxxxxx> know about it.
>From 70471860ff9f335c60c004d42ebd48945bfa5403 Mon Sep 17 00:00:00 2001
From: Alex Deucher <alexander.deucher@xxxxxxx>
Date: Thu, 31 Oct 2013 16:43:27 -0400
Subject: drm/radeon: don't share PPLLs on DCE4.1
From: Alex Deucher <alexander.deucher@xxxxxxx>
commit 70471860ff9f335c60c004d42ebd48945bfa5403 upstream.
Sharing PPLLs seems to cause problems on some boards.
Bug:
https://bugs.freedesktop.org/show_bug.cgi?id=45334
Signed-off-by: Alex Deucher <alexander.deucher@xxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/gpu/drm/radeon/atombios_crtc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/gpu/drm/radeon/atombios_crtc.c
+++ b/drivers/gpu/drm/radeon/atombios_crtc.c
@@ -1753,7 +1753,7 @@ static int radeon_atom_pick_pll(struct d
if (pll != ATOM_PPLL_INVALID)
return pll;
}
- } else {
+ } else if (!ASIC_IS_DCE41(rdev)) { /* Don't share PLLs on DCE4.1 chips */
/* use the same PPLL for all monitors with the same clock */
pll = radeon_get_shared_nondp_ppll(crtc);
if (pll != ATOM_PPLL_INVALID)
Patches currently in stable-queue which might be from alexander.deucher@xxxxxxx are
queue-3.12/drm-radeon-don-t-share-pplls-on-dce4.1.patch
queue-3.12/drm-radeon-fix-uvd-destroy-ib-size.patch
queue-3.12/drm-radeon-si-fix-define-for-mc_seq_train_wakeup_cntl.patch
queue-3.12/radeon-i2c-do-not-count-reg-index-in-number-of-i2c-byte-we-are-writing.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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html