drm/omap: increase vblank wait timeout
authorTomi Valkeinen <tomi.valkeinen@ti.com>
Thu, 19 Nov 2015 15:31:25 +0000 (17:31 +0200)
committerTomi Valkeinen <tomi.valkeinen@ti.com>
Thu, 3 Mar 2016 15:36:42 +0000 (17:36 +0200)
omap_crtc_wait_pending() waits until the config changes have been taken
into use, usually at next vblank. The wait-timeout used is 50ms, which
usually is enough, but in some rare cases not.

As time wait-timeout is just a safety measure for cases where something
is broken, we can just as well increase the timeout considerably.

This patch makes the timeout 250ms.

Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
drivers/gpu/drm/omapdrm/omap_crtc.c

index f5b19d18fa8b2cd18dd14a445d655618044c4b16..f1cd2800055b0b1e02b2063b1803d02b2343c390 100644 (file)
@@ -80,9 +80,13 @@ int omap_crtc_wait_pending(struct drm_crtc *crtc)
 {
        struct omap_crtc *omap_crtc = to_omap_crtc(crtc);
 
+       /*
+        * Timeout is set to a "sufficiently" high value, which should cover
+        * a single frame refresh even on slower displays.
+        */
        return wait_event_timeout(omap_crtc->pending_wait,
                                  !omap_crtc->pending,
-                                 msecs_to_jiffies(50));
+                                 msecs_to_jiffies(250));
 }
 
 /* -----------------------------------------------------------------------------