mbox series

[GIT,PULL] drm/imx: fix stale vblank timestamp after a modeset

Message ID 1562237119.6641.16.camel@pengutronix.de (mailing list archive)
State New, archived
Headers show
Series [GIT,PULL] drm/imx: fix stale vblank timestamp after a modeset | expand

Pull-request

git://git.pengutronix.de/git/pza/linux.git tags/imx-drm-fixes-2019-07-04

Message

Philipp Zabel July 4, 2019, 10:45 a.m. UTC
Hi Dave, Daniel,

please consider merging these imx-drm fixes for v5.2.

regards
Philipp

The following changes since commit 4b972a01a7da614b4796475f933094751a295a2f:

  Linux 5.2-rc6 (2019-06-22 16:01:36 -0700)

are available in the git repository at:

  git://git.pengutronix.de/git/pza/linux.git tags/imx-drm-fixes-2019-07-04

for you to fetch changes up to 5aeab2bfc9ffa72d3ca73416635cb3785dfc076f:

  drm/imx: only send event on crtc disable if kept disabled (2019-07-04 12:21:25 +0200)

----------------------------------------------------------------
drm/imx: fix stale vblank timestamp after a modeset

This series fixes stale vblank timestamps in the first event sent after
a crtc was disabled. The core now is notified via drm_crtc_vblank_off
before sending the last pending event in atomic_disable. If the crtc is
reenabled right away during to a modeset, the event is not sent at all,
as the next vblank will take care of it.

----------------------------------------------------------------
Robert Beckett (2):
      drm/imx: notify drm core before sending event during crtc disable
      drm/imx: only send event on crtc disable if kept disabled

 drivers/gpu/drm/imx/ipuv3-crtc.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)