From: Paulo Zanoni <paulo.r.zanoni@xxxxxxxxx> So make sure that, at prepare_test(), we wait for FBC to be enabled again after we run the exec_nop() call. Since after this happens, we just assert fbc_enabled() at test_crc() instead of waiting for it to be enabled. This is now needed because we moved to software frontbuffer tracking, so it can take some considerable time for FBC to be reenabled after it is disabled. A previous version of this patch was just calling gem_sync() after exec_nop(). Signed-off-by: Paulo Zanoni <paulo.r.zanoni@xxxxxxxxx> --- tests/kms_fbc_crc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/tests/kms_fbc_crc.c b/tests/kms_fbc_crc.c index 37527d8..6022a6a 100644 --- a/tests/kms_fbc_crc.c +++ b/tests/kms_fbc_crc.c @@ -383,6 +383,7 @@ static bool prepare_test(data_t *data, enum test_mode test_mode) * FBC RT address is left as disabled. */ exec_nop(data, data->fb[0].gem_handle, data->ctx[0]); + igt_assert(wait_for_fbc_enabled(data)); } igt_wait_for_vblank(data->drm_fd, data->pipe); -- 2.1.4 _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
