Re: [PATCH v2 3/4] drm/atomic: Add drm_atomic_state->duplicated

2019-02-04 Thread Daniel Vetter
On Fri, Feb 01, 2019 at 05:41:58PM -0500, Lyude Paul wrote: > Important! below > > On Fri, 2019-02-01 at 18:57 +0100, Daniel Vetter wrote: > > On Thu, Jan 31, 2019 at 08:14:50PM -0500, Lyude Paul wrote: > > > Since > > > > > > commit 39b50c603878 ("drm/atomic_helper: Stop modesets on unregistered

Re: [PATCH v2 3/4] drm/atomic: Add drm_atomic_state->duplicated

2019-02-01 Thread Lyude Paul
Important! below On Fri, 2019-02-01 at 18:57 +0100, Daniel Vetter wrote: > On Thu, Jan 31, 2019 at 08:14:50PM -0500, Lyude Paul wrote: > > Since > > > > commit 39b50c603878 ("drm/atomic_helper: Stop modesets on unregistered > > connectors harder") > > > > We've been failing atomic checks if they

Re: [PATCH v2 3/4] drm/atomic: Add drm_atomic_state->duplicated

2019-02-01 Thread Daniel Vetter
On Thu, Jan 31, 2019 at 08:14:50PM -0500, Lyude Paul wrote: > Since > > commit 39b50c603878 ("drm/atomic_helper: Stop modesets on unregistered > connectors harder") > > We've been failing atomic checks if they try to enable new displays on > unregistered connectors. This is fine except for the on

[PATCH v2 3/4] drm/atomic: Add drm_atomic_state->duplicated

2019-01-31 Thread Lyude Paul
Since commit 39b50c603878 ("drm/atomic_helper: Stop modesets on unregistered connectors harder") We've been failing atomic checks if they try to enable new displays on unregistered connectors. This is fine except for the one situation that breaks atomic assumptions: suspend/resume. If a connector