drm/imx: move arming of the vblank event to atomic_flush
authorLucas Stach <l.stach@pengutronix.de>
Thu, 15 Mar 2018 09:11:59 +0000 (10:11 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 30 May 2018 05:50:37 +0000 (07:50 +0200)
commitb43e24b039364fdab601a020103ae55d4e0f7dea
tree1e228e3f18b0607bb9a2a66058cf48eef022555f
parente1e08390525aba7df545ac29ef9379593d0caa94
drm/imx: move arming of the vblank event to atomic_flush

[ Upstream commit 6a055b92de15af987b4027826d43aa103c65a3c4 ]

Right now the vblank event completion is racing with the atomic update,
which is especially bad when the PRE is in use, as one of the hardware
issue workaround might extend the atomic commit for quite some time.

If the vblank IRQ happens to trigger during that time, we will prematurely
signal the atomic commit completion to userspace, which causes tearing
when userspace re-uses a framebuffer we haven't managed to flip away from
yet.

Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
Signed-off-by: Sasha Levin <alexander.levin@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/gpu/drm/imx/ipuv3-crtc.c