summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/drm_auth.c
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2015-09-14 22:43:51 +0300
committerDaniel Vetter <daniel.vetter@ffwll.ch>2015-09-24 20:14:24 +0200
commit4dfd64862ff852df7b1198d667dda778715ee88f (patch)
tree946cd82e93c5ff4b8aed196810eb3e46630a977e /drivers/gpu/drm/drm_auth.c
parent1b2eb71050915d88e62a0ca0c448e0e93484ae9e (diff)
downloadtalos-op-linux-4dfd64862ff852df7b1198d667dda778715ee88f.tar.gz
talos-op-linux-4dfd64862ff852df7b1198d667dda778715ee88f.zip
drm: Use vblank timestamps to guesstimate how many vblanks were missed
When lacking am accurate hardware frame counter, we can fall back to using the vblank timestamps to guesstimagte how many vblanks have elapsed since the last time the vblank counter was updated. Take the oppostunity to unify the vblank_disable_and_save() and drm_handle_vblank_events() to call the same function (drm_update_vblank_count()) to perform the vblank updates. If the hardware/driver has an accurate frame counter use it instead of the timestamp based guesstimate. If the hardware/driver has neither a frame counter nor acurate vblank timestamps, we fall back to assuming that each drm_handle_vblank_events() should increment the vblank count by one. Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/gpu/drm/drm_auth.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud