drm/i915: Use the correct IRQ during resume
authorThomas Zimmermann <tzimmermann@suse.de>
Thu, 1 Jul 2021 17:36:17 +0000 (19:36 +0200)
committerRodrigo Vivi <rodrigo.vivi@intel.com>
Tue, 6 Jul 2021 19:10:58 +0000 (15:10 -0400)
The code in xcs_resume() probably didn't work as intended. It uses
struct drm_device.irq, which is allocated to 0, but never initialized
by i915 to the device's interrupt number.

Change all calls to synchronize_hardirq() to intel_synchronize_irq(),
which uses the correct interrupt. _hardirq() functions are not needed
in this context.

v5:
* go back to _hardirq() after PCI probe reported wrong
  context; add rsp comment
v4:
* switch everything to intel_synchronize_irq() (Daniel)
v3:
* also use intel_synchronize_hardirq() at another callsite
v2:
* wrap irq code in intel_synchronize_hardirq() (Ville)

Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Fixes: 536f77b1caa0 ("drm/i915/gt: Call stop_ring() from ring resume, again")
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/20210701173618.10718-2-tzimmermann@suse.de
(cherry picked from commit 27e4b467d94e216b365da388358c9407af818662)
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
drivers/gpu/drm/i915/gt/intel_engine_cs.c
drivers/gpu/drm/i915/gt/intel_ring_submission.c
drivers/gpu/drm/i915/i915_irq.c
drivers/gpu/drm/i915/i915_irq.h

index 9ceddfbb1687d64d0b7aeffc2c233132bc5ad32e..7f03df2366137980cf9747bc5f82712013d60974 100644 (file)
@@ -1279,7 +1279,7 @@ bool intel_engine_is_idle(struct intel_engine_cs *engine)
                return true;
 
        /* Waiting to drain ELSP? */
-       synchronize_hardirq(to_pci_dev(engine->i915->drm.dev)->irq);
+       intel_synchronize_hardirq(engine->i915);
        intel_engine_flush_submission(engine);
 
        /* ELSP is empty, but there are ready requests? E.g. after reset */
index 0c423f096e2ba36681dd4597f47a4eefd0dafc39..37d74d4ed59b8f15ef07a58e93e6c3779f5ef1ec 100644 (file)
@@ -184,8 +184,11 @@ static int xcs_resume(struct intel_engine_cs *engine)
        ENGINE_TRACE(engine, "ring:{HEAD:%04x, TAIL:%04x}\n",
                     ring->head, ring->tail);
 
-       /* Double check the ring is empty & disabled before we resume */
-       synchronize_hardirq(engine->i915->drm.irq);
+       /*
+        * Double check the ring is empty & disabled before we resume. Called
+        * from atomic context during PCI probe, so _hardirq().
+        */
+       intel_synchronize_hardirq(engine->i915);
        if (!stop_ring(engine))
                goto err;
 
index a11bdb6672418753c8bae9db5ef77ef4d7893186..7d13d214705403d704dc06d732e7e104bdcc6239 100644 (file)
@@ -4575,3 +4575,8 @@ void intel_synchronize_irq(struct drm_i915_private *i915)
 {
        synchronize_irq(to_pci_dev(i915->drm.dev)->irq);
 }
+
+void intel_synchronize_hardirq(struct drm_i915_private *i915)
+{
+       synchronize_hardirq(to_pci_dev(i915->drm.dev)->irq);
+}
index db34d5dbe402bdc40819718f5e3ef3a49fc562f6..e43b6734f21b73c917e7ce6226ef45d1e16b9bdb 100644 (file)
@@ -94,6 +94,7 @@ void intel_runtime_pm_disable_interrupts(struct drm_i915_private *dev_priv);
 void intel_runtime_pm_enable_interrupts(struct drm_i915_private *dev_priv);
 bool intel_irqs_enabled(struct drm_i915_private *dev_priv);
 void intel_synchronize_irq(struct drm_i915_private *i915);
+void intel_synchronize_hardirq(struct drm_i915_private *i915);
 
 int intel_get_crtc_scanline(struct intel_crtc *crtc);
 void gen8_irq_power_well_post_enable(struct drm_i915_private *dev_priv,