[PATCH] drm/atomic-helper: Do not call ->mode_fixup for CRTC which will be disabled

2016-05-30 Thread Ying Liu
On Mon, May 30, 2016 at 4:46 PM, Daniel Vetter wrote: > On Fri, May 27, 2016 at 05:35:54PM +0800, Liu Ying wrote: >> When a CRTC is going to be disabled, it's state may contain a display mode >> with zeroed content. This could be reproduced by HDMI cable hotplug out >> operation with legacy fbdev

[PATCH] drm/atomic-helper: Do not call ->mode_fixup for CRTC which will be disabled

2016-05-30 Thread Daniel Vetter
On Fri, May 27, 2016 at 05:35:54PM +0800, Liu Ying wrote: > When a CRTC is going to be disabled, it's state may contain a display mode > with zeroed content. This could be reproduced by HDMI cable hotplug out > operation with legacy fbdev support in dual display cases. It would confuse > driver's

[PATCH] drm/atomic-helper: Do not call ->mode_fixup for CRTC which will be disabled

2016-05-27 Thread Liu Ying
When a CRTC is going to be disabled, it's state may contain a display mode with zeroed content. This could be reproduced by HDMI cable hotplug out operation with legacy fbdev support in dual display cases. It would confuse driver's CRTC callback ->mode_fixup and make the total state be rejected.