diff options
| author | Mario Kleiner <[email protected]> | 2014-09-13 18:25:54 +0200 |
|---|---|---|
| committer | Daniel Vetter <[email protected]> | 2014-09-24 12:09:22 +0200 |
| commit | da8f43962bd323813f7215b00b5da48ad766b9b2 (patch) | |
| tree | 88971e62a2687641d9036acf8dfc5f8633723687 /scripts/gdb/linux/utils.py | |
| parent | d743ecf360637d489a3ba81a268f574359149601 (diff) | |
drm: Don't update vblank timestamp when the counter didn't change
If we already have a timestamp for the current vblank counter, don't
update it with a new timestmap. Small errors can creep in between two
timestamp queries for the same vblank count, which could be confusing to
userspace when it queries the timestamp for the same vblank sequence
number twice.
This problem gets exposed when the vblank disable timer is not used
(or is set to expire quickly) and thus we can get multiple vblank
disable<->enable transition during the same frame which would all
attempt to update the timestamp with the latest estimate.
Testcase: igt/kms_flip/flip-vs-expired-vblank
Signed-off-by: Ville Syrjälä <[email protected]>
Reviewed-by: Mario Kleiner <[email protected]>
v2:Mario: Trivial rebase on top of current drm-next (13-Sep-2014)
Signed-off-by: Mario Kleiner <[email protected]>
Signed-off-by: Daniel Vetter <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions