From: "Christian König" <deathsimple@vodafone.de>
To: alexdeucher@gmail.com
Cc: Alex Deucher <alexander.deucher@amd.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/radeon: fix regression in dynpm due to multi-ring rework
Date: Thu, 14 Jun 2012 22:17:18 +0200 [thread overview]
Message-ID: <4FDA46CE.9080102@vodafone.de> (raw)
In-Reply-To: <1339703697-16413-1-git-send-email-alexdeucher@gmail.com>
On 14.06.2012 21:54, alexdeucher@gmail.com wrote:
> From: Alex Deucher<alexander.deucher@amd.com>
>
> Not all asics have all rings, so make sure the ring is ready
> before attempting to check it in the dynpm work handler.
>
> Fixes:
> https://bugzilla.kernel.org/show_bug.cgi?id=43367
>
> Signed-off-by: Alex Deucher<alexander.deucher@amd.com>
Reviewed-by: Christian König<christian.koenig@amd.com>
> ---
> drivers/gpu/drm/radeon/radeon_pm.c | 10 +++++++---
> 1 files changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_pm.c b/drivers/gpu/drm/radeon/radeon_pm.c
> index 79642cd..7ae6066 100644
> --- a/drivers/gpu/drm/radeon/radeon_pm.c
> +++ b/drivers/gpu/drm/radeon/radeon_pm.c
> @@ -793,9 +793,13 @@ static void radeon_dynpm_idle_work_handler(struct work_struct *work)
> int i;
>
> for (i = 0; i< RADEON_NUM_RINGS; ++i) {
> - not_processed += radeon_fence_count_emitted(rdev, i);
> - if (not_processed>= 3)
> - break;
> + struct radeon_ring *ring =&rdev->ring[i];
> +
> + if (ring->ready) {
> + not_processed += radeon_fence_count_emitted(rdev, i);
> + if (not_processed>= 3)
> + break;
> + }
> }
>
> if (not_processed>= 3) { /* should upclock */
next prev parent reply other threads:[~2012-06-14 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 19:54 [PATCH] drm/radeon: fix regression in dynpm due to multi-ring rework alexdeucher
2012-06-14 19:58 ` Jerome Glisse
2012-06-14 20:17 ` Christian König [this message]
2012-06-14 20:35 ` Stripping of spaces in messages (was: [PATCH] drm/radeon: fix regression in dynpm due to multi-ring rework) Paul Menzel
2012-06-14 20:51 ` Stripping of spaces in messages Christian König
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=4FDA46CE.9080102@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.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.