[Intel-gfx] [PATCH v2 5/6] drm/atomic: Handle encoder assignment conflicts in a separate check.

On Tue, Mar 01, 2016 at 06:45:53PM +0100, Maarten Lankhorst wrote: > Op 01-03-16 om 18:21 schreef Ville Syrjälä: > > On Wed, Feb 24, 2016 at 09:37:32AM +0100, Maarten Lankhorst wrote: > >> The current check doesn't handle the case where we don't steal an > >> encoder, but keep it on the current c

[Intel-gfx] [PATCH v2 5/6] drm/atomic: Handle encoder assignment conflicts in a separate check.

On Wed, Feb 24, 2016 at 09:37:32AM +0100, Maarten Lankhorst wrote: > The current check doesn't handle the case where we don't steal an > encoder, but keep it on the current connector. If we repurpose > disable_conflicting_encoders to do the checking, we just have > to reject the ones that conflict.

[Intel-gfx] [PATCH v2 5/6] drm/atomic: Handle encoder assignment conflicts in a separate check.

Op 01-03-16 om 18:21 schreef Ville Syrjälä: > On Wed, Feb 24, 2016 at 09:37:32AM +0100, Maarten Lankhorst wrote: >> The current check doesn't handle the case where we don't steal an >> encoder, but keep it on the current connector. If we repurpose >> disable_conflicting_encoders to do the checkin

[PATCH v2 5/6] drm/atomic: Handle encoder assignment conflicts in a separate check.

The current check doesn't handle the case where we don't steal an encoder, but keep it on the current connector. If we repurpose disable_conflicting_encoders to do the checking, we just have to reject the ones that conflict. Signed-off-by: Maarten Lankhorst Testcase: kms_setmode.invalid-clone-sin