On Mon, Aug 18, 2014 at 4:02 PM, Maarten Lankhorst <maarten.lankhorst at canonical.com> wrote: > Hey, > > On 18-08-14 18:10, Alex Deucher wrote: >> On Mon, Aug 18, 2014 at 12:07 PM, Christian K?nig >> <deathsimple at vodafone.de> wrote: >>>> Yeah, looks like a bug. I think the attached patch should fix it. >>> >>> Sounds logical and the patch is Reviewed-by: Christian K?nig >>> <christian.koenig at amd.com> >>> >>> Going to apply Maartens patch on top and test that one a bit to make sure it >>> works as expected. >> >> pushed my current -fixes queue to my drm-fixes-3.17-wip branch if that helps. > > Thanks, maybe that fixes uvd on resume for me. :-) > > I'll have to rework it to include the changes, but does resuming everything > in the order of my v2 patch look sane? > Then as a final act I'm downgrading to read, and run the tests.
Seems sane. Looks like we probably also need this attached patch as well to be on the safe side for displays. It would be nice to unify the suspend/resume and gpu_reset paths at some point. Alex -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-drm-radeon-fix-display-handling-in-radeon_gpu_reset.patch Type: text/x-diff Size: 1677 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140818/83bbb64f/attachment.patch>
