From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 4/5] drm/i915/irq: hide display_irqs_enabled access
Date: Fri, 15 Nov 2024 14:10:25 -0500 [thread overview]
Message-ID: <ZzecoVjYtoa4omwT@intel.com> (raw)
In-Reply-To: <8734js63no.fsf@intel.com>
On Fri, Nov 15, 2024 at 03:13:31PM +0200, Jani Nikula wrote:
> On Thu, 14 Nov 2024, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> > On Mon, Nov 11, 2024 at 07:53:33PM +0200, Jani Nikula wrote:
> >> Move the check for display_irqs_enabled within vlv_display_irq_reset()
> >> and vlv_display_irq_postinstall() to avoid looking at struct
> >> intel_display members within i915 core irq code.
> >>
> >> Within display irq code, vlv_display_irq_reset() may need to be called
> >> with !display_irqs_enabled, so add a small wrapper.
> >>
> >> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> >> ---
> >> drivers/gpu/drm/i915/display/intel_display_irq.c | 15 ++++++++++++---
> >> drivers/gpu/drm/i915/i915_irq.c | 12 ++++--------
> >> 2 files changed, 16 insertions(+), 11 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/i915/display/intel_display_irq.c b/drivers/gpu/drm/i915/display/intel_display_irq.c
> >> index e1547ebce60e..d5458b0d976b 100644
> >> --- a/drivers/gpu/drm/i915/display/intel_display_irq.c
> >> +++ b/drivers/gpu/drm/i915/display/intel_display_irq.c
> >> @@ -1479,7 +1479,7 @@ void bdw_disable_vblank(struct drm_crtc *_crtc)
> >> schedule_work(&display->irq.vblank_dc_work);
> >> }
> >>
> >> -void vlv_display_irq_reset(struct drm_i915_private *dev_priv)
> >> +static void _vlv_display_irq_reset(struct drm_i915_private *dev_priv)
> >> {
> >> struct intel_uncore *uncore = &dev_priv->uncore;
> >>
> >> @@ -1497,6 +1497,12 @@ void vlv_display_irq_reset(struct drm_i915_private *dev_priv)
> >> dev_priv->irq_mask = ~0u;
> >> }
> >>
> >> +void vlv_display_irq_reset(struct drm_i915_private *dev_priv)
> >> +{
> >> + if (dev_priv->display.irq.display_irqs_enabled)
> >> + _vlv_display_irq_reset(dev_priv);
> >> +}
> >> +
> >> void i9xx_display_irq_reset(struct drm_i915_private *i915)
> >> {
> >> if (I915_HAS_HOTPLUG(i915)) {
> >> @@ -1516,6 +1522,9 @@ void vlv_display_irq_postinstall(struct drm_i915_private *dev_priv)
> >> u32 enable_mask;
> >> enum pipe pipe;
> >>
> >> + if (!dev_priv->display.irq.display_irqs_enabled)
> >> + return;
> >
> > I got confused here. this likely deserves a separate patch?
>
> I thought I explained it in the commit message. The check is being moved
> from the callers to the callees. But for vlv_display_irq_reset() we also
> need to be able to call without the check, so that gets an additional
> wrapper.
doh!
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> BR,
> Jani.
>
> >
> >> +
> >> pipestat_mask = PIPE_CRC_DONE_INTERRUPT_STATUS;
> >>
> >> i915_enable_pipestat(dev_priv, PIPE_A, PIPE_GMBUS_INTERRUPT_STATUS);
> >> @@ -1694,7 +1703,7 @@ void valleyview_enable_display_irqs(struct drm_i915_private *dev_priv)
> >> dev_priv->display.irq.display_irqs_enabled = true;
> >>
> >> if (intel_irqs_enabled(dev_priv)) {
> >> - vlv_display_irq_reset(dev_priv);
> >> + _vlv_display_irq_reset(dev_priv);
> >> vlv_display_irq_postinstall(dev_priv);
> >> }
> >> }
> >> @@ -1709,7 +1718,7 @@ void valleyview_disable_display_irqs(struct drm_i915_private *dev_priv)
> >> dev_priv->display.irq.display_irqs_enabled = false;
> >>
> >> if (intel_irqs_enabled(dev_priv))
> >> - vlv_display_irq_reset(dev_priv);
> >> + _vlv_display_irq_reset(dev_priv);
> >> }
> >>
> >> void ilk_de_irq_postinstall(struct drm_i915_private *i915)
> >> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> >> index f75cbf5b8a1c..7920ad9585ae 100644
> >> --- a/drivers/gpu/drm/i915/i915_irq.c
> >> +++ b/drivers/gpu/drm/i915/i915_irq.c
> >> @@ -658,8 +658,7 @@ static void valleyview_irq_reset(struct drm_i915_private *dev_priv)
> >> gen5_gt_irq_reset(to_gt(dev_priv));
> >>
> >> spin_lock_irq(&dev_priv->irq_lock);
> >> - if (dev_priv->display.irq.display_irqs_enabled)
> >> - vlv_display_irq_reset(dev_priv);
> >> + vlv_display_irq_reset(dev_priv);
> >> spin_unlock_irq(&dev_priv->irq_lock);
> >> }
> >>
> >> @@ -723,8 +722,7 @@ static void cherryview_irq_reset(struct drm_i915_private *dev_priv)
> >> gen2_irq_reset(uncore, GEN8_PCU_IRQ_REGS);
> >>
> >> spin_lock_irq(&dev_priv->irq_lock);
> >> - if (dev_priv->display.irq.display_irqs_enabled)
> >> - vlv_display_irq_reset(dev_priv);
> >> + vlv_display_irq_reset(dev_priv);
> >> spin_unlock_irq(&dev_priv->irq_lock);
> >> }
> >>
> >> @@ -740,8 +738,7 @@ static void valleyview_irq_postinstall(struct drm_i915_private *dev_priv)
> >> gen5_gt_irq_postinstall(to_gt(dev_priv));
> >>
> >> spin_lock_irq(&dev_priv->irq_lock);
> >> - if (dev_priv->display.irq.display_irqs_enabled)
> >> - vlv_display_irq_postinstall(dev_priv);
> >> + vlv_display_irq_postinstall(dev_priv);
> >> spin_unlock_irq(&dev_priv->irq_lock);
> >>
> >> intel_uncore_write(&dev_priv->uncore, VLV_MASTER_IER, MASTER_INTERRUPT_ENABLE);
> >> @@ -794,8 +791,7 @@ static void cherryview_irq_postinstall(struct drm_i915_private *dev_priv)
> >> gen8_gt_irq_postinstall(to_gt(dev_priv));
> >>
> >> spin_lock_irq(&dev_priv->irq_lock);
> >> - if (dev_priv->display.irq.display_irqs_enabled)
> >> - vlv_display_irq_postinstall(dev_priv);
> >> + vlv_display_irq_postinstall(dev_priv);
> >> spin_unlock_irq(&dev_priv->irq_lock);
> >>
> >> intel_uncore_write(&dev_priv->uncore, GEN8_MASTER_IRQ, GEN8_MASTER_IRQ_CONTROL);
> >> --
> >> 2.39.5
> >>
>
> --
> Jani Nikula, Intel
next prev parent reply other threads:[~2024-11-15 19:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 17:53 [PATCH 0/5] drm/i915: intel_display conversions, cleanups Jani Nikula
2024-11-11 17:53 ` [PATCH 1/5] drm/i915/overlay: convert to struct intel_display Jani Nikula
2024-11-12 20:40 ` Rodrigo Vivi
2024-11-13 8:26 ` Jani Nikula
2024-11-11 17:53 ` [PATCH 2/5] drm/i915/overlay: add intel_overlay_available() and use it Jani Nikula
2024-11-14 17:51 ` Rodrigo Vivi
2024-11-11 17:53 ` [PATCH 3/5] drm/i915/plane: convert initial plane setup to struct intel_display Jani Nikula
2024-11-14 17:52 ` Rodrigo Vivi
2024-11-11 17:53 ` [PATCH 4/5] drm/i915/irq: hide display_irqs_enabled access Jani Nikula
2024-11-14 17:55 ` Rodrigo Vivi
2024-11-15 13:13 ` Jani Nikula
2024-11-15 19:10 ` Rodrigo Vivi [this message]
2024-11-11 17:53 ` [PATCH 5/5] drm/i915/irq: emphasize display_irqs_enabled is only about VLV/CHV Jani Nikula
2024-11-14 17:57 ` Rodrigo Vivi
2024-11-15 13:15 ` Jani Nikula
2024-11-15 19:11 ` Rodrigo Vivi
2024-11-11 19:00 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: intel_display conversions, cleanups Patchwork
2024-11-11 19:00 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-11 19:01 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-11-18 17:49 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: intel_display conversions, cleanups (rev2) Patchwork
2024-11-18 17:49 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-18 18:08 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-11-19 13:15 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: intel_display conversions, cleanups (rev3) Patchwork
2024-11-19 13:16 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-19 13:31 ` ✗ Fi.CI.BAT: failure " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZzecoVjYtoa4omwT@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).