diff options
| author | Daniele Ceraolo Spurio <[email protected]> | 2019-09-18 18:53:30 -0700 |
|---|---|---|
| committer | Chris Wilson <[email protected]> | 2019-09-19 11:04:55 +0100 |
| commit | 0d333ac7eb17f0f6c86db66afba70135f11da4a9 (patch) | |
| tree | 0c3caf6974f8711778a63569ebfada22b420b9d5 /tools/perf/scripts/python | |
| parent | 56c05de6bd773b96deca379370965c49042b5fbf (diff) | |
drm/i915: fix SFC reset flow
Our assumption that the we can ask the HW to lock the SFC even if not
currently in use does not match the HW commitment. The expectation from
the HW is that SW will not try to lock the SFC if the engine is not
using it and if we do that the behavior is undefined; on ICL the HW
ends up to returning the ack and ignoring our lock request, but this is
not guaranteed and we shouldn't expect it going forward.
Also, failing to get the ack while the SFC is in use means that we can't
cleanly reset it, so fail the engine reset in that scenario.
v2: drop rmw change, keep the log as debug and handle failure (Chris),
improve comments (Tvrtko).
Reported-by: Owen Zhang <[email protected]>
Signed-off-by: Daniele Ceraolo Spurio <[email protected]>
Cc: Tvrtko Ursulin <[email protected]>
Cc: Chris Wilson <[email protected]>
Reviewed-by: Tvrtko Ursulin <[email protected]>
Acked-by: Chris Wilson <[email protected]>
Signed-off-by: Chris Wilson <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions