On 30/03/17 03:45 PM, Zhu, Rex wrote:
> Yes, we tried to fix it. it is a timing issue.
> But it was not a critical error. So no need to block gpu resume.
>
> In fact, We only return error when the last ring test failed in the original
> logic
That makes some sense to me, but at least the commit
: Thursday, March 30, 2017 2:14 PM
To: Zhu, Rex
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/amdgpu: do not block gpu resume when cp ring test
failed.
On 30/03/17 02:42 PM, Rex Zhu wrote:
> As kiq enabled, ring test may randomly failed because of timing.
> it was not c
On 30/03/17 02:42 PM, Rex Zhu wrote:
> As kiq enabled, ring test may randomly failed because of timing.
> it was not critial error, gpu can continue to resume.
>
> Change-Id: I5d85c7d5b5989dd6892a13b47a5322b33e8a48ac
> Signed-off-by: Rex Zhu
> ---
> drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c | 3 +--
As kiq enabled, ring test may randomly failed because of timing.
it was not critial error, gpu can continue to resume.
Change-Id: I5d85c7d5b5989dd6892a13b47a5322b33e8a48ac
Signed-off-by: Rex Zhu
---
drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
di
