Bug 101053

Summary: DC R9 285 fullscreen video regression since drm/amd/display: Parse scanline registers
Product: DRI Reporter: Andy Furniss <adf.lists>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium CC: harry.wentland
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
fix scanline params none

Description Andy Furniss 2017-05-15 21:51:59 UTC 
R9 285 tonga since

commit afbeb2d0961b2139bcf6553a710e6a8ae5d09d34
Author: Sylvia Tsai <sylvia.tsai@amd.com>
Date:   Tue Apr 11 15:15:28 2017 -0400

    drm/amd/display: Parse scanline registers
    
    They could differ between ASIC generations
    
    Change-Id: Ia352ae206273fe3a025579554cae4e3711a26fcc

on agd5f drm staging 4.9/11 there is a regression with full screen video.

mpv --vo=vaapi/vdpau/opengl all the same, dropping frames, or playing slowmo with --framedrop=no

Windowed playback is OK, testing with 60fps vid on 60Hz DVI-D display.

Forcing clocks high does not help.
Comment 1 Harry Wentland 2017-05-16 16:00:40 UTC 
Created attachment 131374 [details] [review]
fix scanline params

Thanks, Andy. Please try attached patch. The regression change you mentioned contains some bad code (that I wrote -_-).
Comment 2 Andy Furniss 2017-05-16 17:09:59 UTC 
That fixes it, thanks.
Comment 3 Harry Wentland 2017-05-16 17:12:08 UTC 
Thanks for testing. It should land in amd-staging-4.9 in a week or so.
Comment 4 Andy Furniss 2017-06-05 18:24:20 UTC 
(In reply to Harry Wentland from comment #3)
> Thanks for testing. It should land in amd-staging-4.9 in a week or so.

Closed by Alex, but AFAICT the fix is only in amd-staging-4.11. 4.9 doesn't seem to have been touched for 4 weeks (unless cgit is wrong).
Comment 5 Alex Deucher 2017-06-05 20:00:26 UTC 
We've moved amd-staging to 4.11 and are not updating the 4.9 branch any more.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.