From: jimqu <Jim.Qu-5C7GfCeVMHo@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: jimqu <Jim.Qu-5C7GfCeVMHo@public.gmane.org>
Subject: [PATCH 1/3] drm/amd/amdgpu: VCE ring test fail during S4 on CI
Date: Tue, 30 Aug 2016 09:21:49 +0800 [thread overview]
Message-ID: <1472520111-17899-2-git-send-email-Jim.Qu@amd.com> (raw)
In-Reply-To: <1472520111-17899-1-git-send-email-Jim.Qu-5C7GfCeVMHo@public.gmane.org>
Set up the VCE clock no matter dpm is enabled or not.
Change-Id: I68e315f8b62c6e3a8636bc5e14036ecc11d980b4
Signed-off-by: JimQu <Jim.Qu@amd.com>
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c
index 9b71d6c..50993df 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c
@@ -812,11 +812,13 @@ int amdgpu_vce_ring_test_ring(struct amdgpu_ring *ring)
unsigned i;
int r;
+ amdgpu_asic_set_vce_clocks(adev, 53300, 40000);
+
r = amdgpu_ring_alloc(ring, 16);
if (r) {
DRM_ERROR("amdgpu: vce failed to lock ring %d (%d).\n",
ring->idx, r);
- return r;
+ goto done;
}
amdgpu_ring_write(ring, VCE_CMD_END);
amdgpu_ring_commit(ring);
@@ -836,6 +838,9 @@ int amdgpu_vce_ring_test_ring(struct amdgpu_ring *ring)
r = -ETIMEDOUT;
}
+done:
+ amdgpu_asic_set_vce_clocks(adev, 0, 0);
+
return r;
}
--
1.9.1
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2016-08-30 1:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 1:21 [PATCH 0/3] S4 issue on CI jimqu
[not found] ` <1472520111-17899-1-git-send-email-Jim.Qu-5C7GfCeVMHo@public.gmane.org>
2016-08-30 1:21 ` jimqu [this message]
[not found] ` <1472520111-17899-2-git-send-email-Jim.Qu-5C7GfCeVMHo@public.gmane.org>
2016-08-30 7:41 ` [PATCH 1/3] drm/amd/amdgpu: VCE ring test fail during S4 " Christian König
2016-08-30 1:21 ` [PATCH 2/3] drm/amd/amdgpu: sdma resume " jimqu
[not found] ` <1472520111-17899-3-git-send-email-Jim.Qu-5C7GfCeVMHo@public.gmane.org>
2016-08-30 5:39 ` Alex Deucher
2016-08-30 1:21 ` [PATCH 3/3] drm/amd/amdgpu: compute ring test " jimqu
[not found] ` <1472520111-17899-4-git-send-email-Jim.Qu-5C7GfCeVMHo@public.gmane.org>
2016-08-30 5:43 ` 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=1472520111-17899-2-git-send-email-Jim.Qu@amd.com \
--to=jim.qu-5c7gfcevmho@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.