Now that we manually steer multicast register reads during workaround
verification, it should be safe to verify these ones too.

Signed-off-by: Matt Roper <matthew.d.ro...@intel.com>
---
 drivers/gpu/drm/i915/gt/intel_workarounds.c | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/drivers/gpu/drm/i915/gt/intel_workarounds.c 
b/drivers/gpu/drm/i915/gt/intel_workarounds.c
index 73a3937c689b..d1b7a445f2da 100644
--- a/drivers/gpu/drm/i915/gt/intel_workarounds.c
+++ b/drivers/gpu/drm/i915/gt/intel_workarounds.c
@@ -1812,13 +1812,9 @@ static int engine_wa_list_verify(struct intel_context 
*ce,
        }
 
        err = 0;
-       for (i = 0, wa = wal->list; i < wal->count; i++, wa++) {
-               if (mcr_range(rq->i915, i915_mmio_reg_offset(wa->reg)))
-                       continue;
-
+       for (i = 0, wa = wal->list; i < wal->count; i++, wa++)
                if (!wa_verify(rq->i915, wa, results[i], wal->name, from))
                        err = -ENXIO;
-       }
 
        i915_gem_object_unpin_map(vma->obj);
 
-- 
2.24.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Reply via email to