Re: [PATCH 2/2] Revert "drm/amd/display: disable CRTCs with NULL FB on their primary plane (V2)"

On 2018-04-13 03:15 AM, Michel Dänzer wrote: > On 2018-04-13 04:55 AM, S, Shirish wrote: >> Hi Harry, Alex, >> >> The solution given while reviewing my patch was that "DC should support >> enabling a CRTC without a framebuffer." > > I think it's weird that an enabled CRTC would end up having a

Re: [PATCH 2/2] Revert "drm/amd/display: disable CRTCs with NULL FB on their primary plane (V2)"

On 2018-04-13 04:55 AM, S, Shirish wrote: > Hi Harry, Alex, > > The solution given while reviewing my patch was that "DC should support > enabling a CRTC without a framebuffer." I think it's weird that an enabled CRTC would end up having a NULL FB during normal operation in the first place. Any

RE: [PATCH 2/2] Revert "drm/amd/display: disable CRTCs with NULL FB on their primary plane (V2)"

9 PM To: Wentland, Harry <harry.wentl...@amd.com> Cc: amd-gfx@lists.freedesktop.org; Deucher, Alexander <alexander.deuc...@amd.com>; S, Shirish <shiris...@amd.com> Subject: Re: [PATCH 2/2] Revert "drm/amd/display: disable CRTCs with NULL FB on their primary plane (V2)

Re: [PATCH 2/2] Revert "drm/amd/display: disable CRTCs with NULL FB on their primary plane (V2)"

On 2018-04-12 04:51 PM, Harry Wentland wrote: > This seems to cause flickering and lock-ups for a wide range of users. > Revert until we've found a proper fix for the flickering and lock-ups. > > This reverts commit 36cc549d59864b7161f0e23d710c1c4d1b9cf022. > > Cc: Shirish S