drm/exynos: track vblank events on a per crtc basis
authorMandeep Singh Baines <msb@chromium.org>
Wed, 1 Apr 2015 16:02:12 +0000 (13:02 -0300)
committerInki Dae <inki.dae@samsung.com>
Mon, 13 Apr 2015 02:39:40 +0000 (11:39 +0900)
commite752747b98ae64ff0d1484a3b1b812fd2cafed53
tree96df2f45f0ade72739061e4ad5bff6254c169311
parent5d09a67f1c102468ec8116c10bcd79bba6563508
drm/exynos: track vblank events on a per crtc basis

The goal of the change is to make sure we send the vblank event on the
current vblank. My hope is to fix any races that might be causing flicker.
After this change I only see a flicker in the transition plymouth and
X11.

Simplified the code by tracking vblank events on a per-crtc basis. This
allowed me to remove all error paths from the callback. It also allowed
me to remove the vblank wait from the callback.

Signed-off-by: Mandeep Singh Baines <msb@chromium.org>
Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Signed-off-by: Inki Dae <inki.dae@samsung.com>
drivers/gpu/drm/exynos/exynos_drm_crtc.c
drivers/gpu/drm/exynos/exynos_drm_drv.c
drivers/gpu/drm/exynos/exynos_drm_drv.h