On Tue, May 31, 2016 at 12:56:23PM +0200, Daniel Vetter wrote:
> On Tue, May 31, 2016 at 12:17:23PM +0300, Tomi Valkeinen wrote:
> > After commit 027b3f8ba9277410c3191d72d1ed2c6146d8a668 ("drm/modes: stop
> > handling framebuffer special") extra fb refs are left around when doing
> > atomic modeset
On Tue, May 31, 2016 at 12:17:23PM +0300, Tomi Valkeinen wrote:
> After commit 027b3f8ba9277410c3191d72d1ed2c6146d8a668 ("drm/modes: stop
> handling framebuffer special") extra fb refs are left around when doing
> atomic modesetting.
>
> The problem is that the new drm_property_change_valid_get()
After commit 027b3f8ba9277410c3191d72d1ed2c6146d8a668 ("drm/modes: stop
handling framebuffer special") extra fb refs are left around when doing
atomic modesetting.
The problem is that the new drm_property_change_valid_get() does not
return anything in the '**ref' parameter, which causes
'drm_prope
