diff options
| author | Maarten Lankhorst <maarten.lankhorst@linux.intel.com> | 2018-12-11 17:07:22 +0100 |
|---|---|---|
| committer | Maarten Lankhorst <maarten.lankhorst@linux.intel.com> | 2018-12-15 08:45:41 +0100 |
| commit | 90c76cb9bb47a5a3ebb34ad6b1a557bc02d39713 (patch) | |
| tree | 4e5e6e234fe722751b6a19d65e5cfadd73389c65 /include/drm-uapi/drm_fourcc.h | |
| parent | 3915d3e8652365a5b640850d1fbcb3b603d55cb3 (diff) | |
tests/kms_frontbuffer_tracking: Make sure GPU is quiescent before handling assertions, v2.
Typically PSR enables in around 136 ms, but on some tests the we have
to explicitly make sure that the gpu is idle before rendering.
Otherwise, sometimes we wait for the background flusher to finish,
which will take at least a second longer, and causes the wait for
PSR to timeout.
On kms_frontbuffer_tracking:
Starting subtest: psr-2p-scndscrn-shrfb-plflip-blt
psr_active(debugfs_fd, true) took 136ms
psr_active(debugfs_fd, true) took 136ms
psr_active(debugfs_fd, true) took 350ms
psr_active(debugfs_fd, true) took 136ms
psr_active(debugfs_fd, true) took 1598ms
Changes since v1:
- Do not call gem_quiescent_gpu on modesetfrombusy subtest, or we get
a timeout.
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Cc: José Roberto de Souza <jose.souza@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108733
Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> #v1
Diffstat (limited to 'include/drm-uapi/drm_fourcc.h')
0 files changed, 0 insertions, 0 deletions