On Tue, Mar 04, 2014 at 10:16:02AM +0100, Daniel Vetter wrote:
> On Fri, Feb 21, 2014 at 09:03:34PM +0200, ville.syrjala at linux.intel.com
> wrote:
> > From: Ville Syrj?l?
> >
> > If someone holds a vblank reference across the modeset, and after/during
> > the modeset someone tries to grab a vb
On Fri, Feb 21, 2014 at 09:03:34PM +0200, ville.syrjala at linux.intel.com
wrote:
> From: Ville Syrj?l?
>
> If someone holds a vblank reference across the modeset, and after/during
> the modeset someone tries to grab a vblank reference, the current code
> won't re-enable the vblank interrupts. T
On Fri, 21 Feb 2014 21:03:34 +0200
ville.syrjala at linux.intel.com wrote:
> From: Ville Syrj?l?
>
> If someone holds a vblank reference across the modeset, and after/during
> the modeset someone tries to grab a vblank reference, the current code
> won't re-enable the vblank interrupts. That's n
From: Ville Syrj?l?
If someone holds a vblank reference across the modeset, and after/during
the modeset someone tries to grab a vblank reference, the current code
won't re-enable the vblank interrupts. That's not good, so instead allow
the driver to choose whether drm_vblank_get() should always
