tests/kms_fbc_crc: exec_nop() can also invalidate FBC

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@intel.com>
This commit is contained in:
Paulo Zanoni 2015-05-05 17:38:49 -03:00
parent 641d535a03
commit 8c3ac50b00

View File

@ -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);