Paulo Zanoni 036401d42c tests/kms_fbc_crc: increase the FBC wait timeout
Now that we moved to the frontbuffer tracking scheme, it may take a
long time for FBC to be updated after it is invalidated: 300ms is not
enough anymore.

The problem starts when i915_gem_execbuffer2() indirectly calls
intel_fb_obj_invalidate(), which disables FBC. After this, FBC only
gets reenabled when i915_gem_retire_work_handler() happens and
indirectly calls intel_frontbuffer_flush(). Notice that while FBC is
not yet enabled, the screen contents are correct, so this shouldn't
really be a bug.

Previous versions of this patch were replacing the gem_bo_busy() calls
with gem_sync(), but after some discussion we concluded this was not
the correct way to handle the problem, so let's just increase the
timeout so we can kill those subtest failures.

Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
2015-05-14 10:02:07 -03:00
..
2015-05-11 16:19:12 +01:00
2014-12-10 17:11:35 +00:00
2014-12-10 17:11:35 +00:00
2012-04-10 16:23:18 +02:00
2014-05-14 00:36:04 +02:00
2015-02-13 09:35:36 +01:00
2014-12-04 10:17:24 +08:00
2014-05-14 00:36:04 +02:00
2014-12-04 16:07:55 +00:00
2014-05-14 00:36:04 +02:00
2014-05-14 00:36:04 +02:00
2014-06-13 18:27:59 +02:00
2015-03-12 14:15:26 +00:00
2014-12-04 16:07:55 +00:00
2015-04-14 17:43:05 +01:00
2015-05-11 16:19:12 +01:00
2015-05-05 17:27:49 -03:00
2015-03-23 12:50:48 -07:00
2013-11-01 21:10:59 +01:00
2014-06-13 18:27:59 +02:00
2012-01-15 16:05:43 +01:00