aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/i915/intel_tv.c
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2019-01-28 01:02:18 +0000
committerChris Wilson <chris@chris-wilson.co.uk>2019-01-28 09:30:08 +0000
commitad4062da1397e32a942191c61de3eabe1fb3664f (patch)
tree4297bac567d5300aa7b887aa9da1846dbaa12232 /drivers/gpu/drm/i915/intel_tv.c
parentdrm/i915: Disable -Wuninitialized (diff)
downloadlinux-dev-ad4062da1397e32a942191c61de3eabe1fb3664f.tar.xz
linux-dev-ad4062da1397e32a942191c61de3eabe1fb3664f.zip
drm/i915: Wait for a moment before forcibly resetting the device
During igt, we ask to reset the device if any requests are still outstanding at the end of a test, as this quickly kills off any erroneous hanging request streams that may escape a test. However, since it may take the device a few milliseconds to flush itself after the end of a normal test, *cough* guc *cough*, we may accidentally tell the device to reset itself after it idles. If we wait a moment, our usual I915_IDLE_ENGINES_TIMEOUT of 200ms (seems a bit high, but still better than umpteen hangchecks!), we can differentiate better between a stuck engine and a healthy one, and so avoid prematurely forcing the reset and any extra complications that may entail. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Mika Kuoppala <mika.kuoppala@intel.com> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190128010245.20148-1-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/i915/intel_tv.c')
0 files changed, 0 insertions, 0 deletions