This is a note to let you know that I've just added the patch titled
drm/radeon: add additional pci revision to dpm workaround
to the 4.8-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-additional-pci-revision-to-dpm-workaround.patch
and it can be found in the queue-4.8 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 8729675c00a8d13cb2094d617d70a4a4da7d83c5 Mon Sep 17 00:00:00 2001
From: Alex Deucher <alexander.deucher@xxxxxxx>
Date: Fri, 2 Dec 2016 00:21:48 -0500
Subject: drm/radeon: add additional pci revision to dpm workaround
From: Alex Deucher <alexander.deucher@xxxxxxx>
commit 8729675c00a8d13cb2094d617d70a4a4da7d83c5 upstream.
New variant.
Signed-off-by: Alex Deucher <alexander.deucher@xxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/gpu/drm/radeon/si_dpm.c | 1 +
1 file changed, 1 insertion(+)
--- a/drivers/gpu/drm/radeon/si_dpm.c
+++ b/drivers/gpu/drm/radeon/si_dpm.c
@@ -3026,6 +3026,7 @@ static void si_apply_state_adjust_rules(
(rdev->pdev->revision == 0x80) ||
(rdev->pdev->revision == 0x81) ||
(rdev->pdev->revision == 0x83) ||
+ (rdev->pdev->revision == 0x87) ||
(rdev->pdev->device == 0x6604) ||
(rdev->pdev->device == 0x6605)) {
max_sclk = 75000;
Patches currently in stable-queue which might be from alexander.deucher@xxxxxxx are
queue-4.8/drm-amd-amdgpu-enable-gui-idle-int-after-enabling-cgcg.patch
queue-4.8/drm-radeon-add-additional-pci-revision-to-dpm-workaround.patch
queue-4.8/drm-radeon-si-load-the-proper-firmware-on-0x87-oland-boards.patch
queue-4.8/drm-radeon-also-call-cursor_move_locked-when-the-cursor-size-changes.patch
queue-4.8/drm-amdgpu-fix-init-save-restore-list-in-gfx_v8.0.patch
queue-4.8/drm-radeon-hide-the-hw-cursor-while-it-s-out-of-bounds.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