[PATCH] amd/dc/dce100: On dce100, set clocks to 0 on suspend

[Francis, David]

Upon closer inspection, this does not match any FDO bug.  The FDO bug I thought this was related to was fixed by Michel Danzer, and this fixes an entirely separate issue.

________________________________
From: Michel Dänzer <michel at daenzer.net>
Sent: July 12, 2018 10:18:34 AM
To: Wentland, Harry; Francis, David; amd-gfx at lists.freedesktop.org
Subject: Re: [PATCH] amd/dc/dce100: On dce100, set clocks to 0 on suspend

On 2018-07-12 04:13 PM, Harry Wentland wrote:
> On 2018-07-12 10:07 AM, David Francis wrote:
>> [Why]
>> When a dce100 asic was suspended, the clocks were not set to 0.
>> Upon resume, the new clock was compared to the existing clock,
>> they were found to be the same, and so the clock was not set.
>> This resulted in a pernicious blackscreen.
>>
>> [How]
>> In atomic commit, check to see if there are any active pipes.
>> If no, set clocks to 0
>>
>
> Please add Fixes: tag with link to freedesktop bugzilla bug that this fixes.

That would be

Bugzilla: https://...

(the Fixes tag is for referencing another commit which is fixed by this one)


--
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/amd-gfx/attachments/20180712/e08f26c9/attachment-0001.html>