On Wed, Mar 22, 2017 at 04:05:59PM +0200, Jani Nikula wrote:
> On Wed, 22 Mar 2017, Daniel Vetter wrote:
> > On Wed, Mar 22, 2017 at 12:33:35PM +0200, Jani Nikula wrote:
> >> On Wed, 22 Mar 2017, Daniel Vetter wrote:
> >> > There's really no reason for anything more:
> >> > - Calling this while t
On Wed, 22 Mar 2017, Daniel Vetter wrote:
> On Wed, Mar 22, 2017 at 12:33:35PM +0200, Jani Nikula wrote:
>> On Wed, 22 Mar 2017, Daniel Vetter wrote:
>> > There's really no reason for anything more:
>> > - Calling this while the crtc vblank stuff isn't set up is a driver
>> > bug. Those places
On Wed, Mar 22, 2017 at 12:33:35PM +0200, Jani Nikula wrote:
> On Wed, 22 Mar 2017, Daniel Vetter wrote:
> > There's really no reason for anything more:
> > - Calling this while the crtc vblank stuff isn't set up is a driver
> > bug. Those places arlready DRM_ERROR.
> > - Calling this when the c
On Wed, 22 Mar 2017, Daniel Vetter wrote:
> There's really no reason for anything more:
> - Calling this while the crtc vblank stuff isn't set up is a driver
> bug. Those places arlready DRM_ERROR.
> - Calling this when the crtc is off is either a driver bug (callin
> drm_crtc_handle_vblank at