From: Umang Raghuvanshi <u@umangis.me>
To: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@linux.ie>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Cc: Umang Raghuvanshi <u@umangis.me>
Subject: [PATCH] drm/radeon: Fix GPU lockups for the R7 M270
Date: Sat, 11 Mar 2017 21:51:13 +0530 [thread overview]
Message-ID: <20170311162113.7497-1-u@umangis.me> (raw)
Commit 3a69adfe5617 ("drm/radeon: drop oland quirks") removed
quirks for Oland but also caused a regression where M270 GPUs
would go into a lock-up when OpenGL intensive applications were used.
This reverts the change only for the M270 and fixes the lock-ups.
Signed-off-by: Umang Raghuvanshi <u@umangis.me>
---
drivers/gpu/drm/radeon/si_dpm.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/gpu/drm/radeon/si_dpm.c b/drivers/gpu/drm/radeon/si_dpm.c
index d12b8978142f..c2c129eef3c4 100644
--- a/drivers/gpu/drm/radeon/si_dpm.c
+++ b/drivers/gpu/drm/radeon/si_dpm.c
@@ -2984,6 +2984,11 @@ static void si_apply_state_adjust_rules(struct radeon_device *rdev,
(rdev->pdev->device == 0x6667)) {
max_sclk = 75000;
}
+ } else if (rdev->family == CHIP_OLAND && rdev->pdev->device == 0x6604 &&
+ rdev->pdev->revision == 0) {
+ // Fix max_sclk and max_mclk for the Radeon R7 M270
+ max_sclk = 75000;
+ max_mclk = 80000;
}
if (rps->vce_active) {
--
2.12.0
next reply other threads:[~2017-03-11 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 16:21 Umang Raghuvanshi [this message]
2017-03-13 19:30 ` [PATCH] drm/radeon: Fix GPU lockups for the R7 M270 Alex Deucher
2017-03-13 19:30 ` Alex Deucher
2017-03-14 2:42 ` Umang Raghuvanshi
2017-03-14 14:34 ` Alex Deucher
2017-03-14 14:34 ` Alex Deucher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170311162113.7497-1-u@umangis.me \
--to=u@umangis.me \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.