summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
diff options
context:
space:
mode:
authorLouis Li <Ching-shih.Li@amd.com>2019-05-25 06:39:47 +0800
committerAlex Deucher <alexander.deucher@amd.com>2019-06-11 12:39:26 -0500
commit91c9c23e430852d4c927202e0a767bcdb688ef44 (patch)
treef447fbbad942f77a6d81212831590fa80c8e4dc0 /drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
parent77866d54167766371f408b9046c343229bc32304 (diff)
downloadlinux-91c9c23e430852d4c927202e0a767bcdb688ef44.tar.bz2
drm/amdgpu: fix ring test failure issue during s3 in vce 3.0 (V2)
[What] vce ring test fails consistently during resume in s3 cycle, due to mismatch read & write pointers. On debug/analysis its found that rptr to be compared is not being correctly updated/read, which leads to this failure. Below is the failure signature: [drm:amdgpu_vce_ring_test_ring] *ERROR* amdgpu: ring 12 test failed [drm:amdgpu_device_ip_resume_phase2] *ERROR* resume of IP block <vce_v3_0> failed -110 [drm:amdgpu_device_resume] *ERROR* amdgpu_device_ip_resume failed (-110). [How] fetch rptr appropriately, meaning move its read location further down in the code flow. With this patch applied the s3 failure is no more seen for >5k s3 cycles, which otherwise is pretty consistent. V2: remove reduntant fetch of rptr Signed-off-by: Louis Li <Ching-shih.Li@amd.com> Reviewed-by: Christian König <christian.koenig@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_device.c')
0 files changed, 0 insertions, 0 deletions