From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 13/14] drm/i915: extract rps interrupt enable/disable helpers
Date: Thu, 11 Jul 2013 08:20:46 +0200 [thread overview]
Message-ID: <20130711062046.GL6143@phenom.ffwll.local> (raw)
In-Reply-To: <CA+gsUGSVVkkX7Vz-ZAha2_YRGYxsbOOAqQEf1G7pJqOtFXfKYw@mail.gmail.com>
On Wed, Jul 10, 2013 at 06:12:13PM -0300, Paulo Zanoni wrote:
> 2013/7/4 Daniel Vetter <daniel.vetter@ffwll.ch>:
> > This just unifies the vlv code with the snb-hsw code which matched
> > exactly before the VECS enabling.
>
> So now the VLV code is behaving differently. Is that intentional? You
> could write about the implications here.
It's just for consistency that we now also reset GEN6_PMINTRMSK for vlv
and that the additional clearing of the rps event bits in PMIIR now
consistently happens in enable_interrupts. Like I've said in the next
commit message, the PMIIR handling here still smells a bit funny - as long
as we properly clear them at irq install time and keep the actual rps
events masked we should never see PMIIR bits here.
-Daniel
>
>
> >
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > ---
> > drivers/gpu/drm/i915/intel_pm.c | 59 ++++++++++++++++++++---------------------
> > 1 file changed, 29 insertions(+), 30 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > index 96f0872..787a528 100644
> > --- a/drivers/gpu/drm/i915/intel_pm.c
> > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > @@ -3121,13 +3121,10 @@ void valleyview_set_rps(struct drm_device *dev, u8 val)
> > trace_intel_gpu_freq_change(vlv_gpu_freq(dev_priv->mem_freq, val));
> > }
> >
> > -
> > -static void gen6_disable_rps(struct drm_device *dev)
> > +static void gen6_disable_rps_interrupts(struct drm_device *dev)
> > {
> > struct drm_i915_private *dev_priv = dev->dev_private;
> >
> > - I915_WRITE(GEN6_RC_CONTROL, 0);
> > - I915_WRITE(GEN6_RPNSWREQ, 1 << 31);
> > I915_WRITE(GEN6_PMINTRMSK, 0xffffffff);
> > I915_WRITE(GEN6_PMIER, I915_READ(GEN6_PMIER) & ~GEN6_PM_RPS_EVENTS);
> > /* Complete PM interrupt masking here doesn't race with the rps work
> > @@ -3142,23 +3139,23 @@ static void gen6_disable_rps(struct drm_device *dev)
> > I915_WRITE(GEN6_PMIIR, GEN6_PM_RPS_EVENTS);
> > }
> >
> > -static void valleyview_disable_rps(struct drm_device *dev)
> > +static void gen6_disable_rps(struct drm_device *dev)
> > {
> > struct drm_i915_private *dev_priv = dev->dev_private;
> >
> > I915_WRITE(GEN6_RC_CONTROL, 0);
> > - I915_WRITE(GEN6_PMINTRMSK, 0xffffffff);
> > - I915_WRITE(GEN6_PMIER, 0);
> > - /* Complete PM interrupt masking here doesn't race with the rps work
> > - * item again unmasking PM interrupts because that is using a different
> > - * register (PMIMR) to mask PM interrupts. The only risk is in leaving
> > - * stale bits in PMIIR and PMIMR which gen6_enable_rps will clean up. */
> > + I915_WRITE(GEN6_RPNSWREQ, 1 << 31);
> >
> > - spin_lock_irq(&dev_priv->irq_lock);
> > - dev_priv->rps.pm_iir = 0;
> > - spin_unlock_irq(&dev_priv->irq_lock);
> > + gen6_disable_rps_interrupts(dev);
> > +}
> > +
> > +static void valleyview_disable_rps(struct drm_device *dev)
> > +{
> > + struct drm_i915_private *dev_priv = dev->dev_private;
> > +
> > + I915_WRITE(GEN6_RC_CONTROL, 0);
> >
> > - I915_WRITE(GEN6_PMIIR, I915_READ(GEN6_PMIIR));
> > + gen6_disable_rps_interrupts(dev);
> >
> > if (dev_priv->vlv_pctx) {
> > drm_gem_object_unreference(&dev_priv->vlv_pctx->base);
> > @@ -3191,6 +3188,21 @@ int intel_enable_rc6(const struct drm_device *dev)
> > return (INTEL_RC6_ENABLE | INTEL_RC6p_ENABLE);
> > }
> >
> > +static void gen6_enable_rps_interrupts(struct drm_device *dev)
> > +{
> > + struct drm_i915_private *dev_priv = dev->dev_private;
> > +
> > + spin_lock_irq(&dev_priv->irq_lock);
> > + /* FIXME: Our interrupt enabling sequence is bonghits.
> > + * dev_priv->rps.pm_iir really should be 0 here. */
> > + dev_priv->rps.pm_iir = 0;
> > + I915_WRITE(GEN6_PMIMR, I915_READ(GEN6_PMIMR) & ~GEN6_PM_RPS_EVENTS);
> > + I915_WRITE(GEN6_PMIIR, GEN6_PM_RPS_EVENTS);
> > + spin_unlock_irq(&dev_priv->irq_lock);
> > + /* unmask all PM interrupts */
> > + I915_WRITE(GEN6_PMINTRMSK, 0);
> > +}
> > +
> > static void gen6_enable_rps(struct drm_device *dev)
> > {
> > struct drm_i915_private *dev_priv = dev->dev_private;
> > @@ -3319,15 +3331,7 @@ static void gen6_enable_rps(struct drm_device *dev)
> >
> > gen6_set_rps(dev_priv->dev, (gt_perf_status & 0xff00) >> 8);
> >
> > - spin_lock_irq(&dev_priv->irq_lock);
> > - /* FIXME: Our interrupt enabling sequence is bonghits.
> > - * dev_priv->rps.pm_iir really should be 0 here. */
> > - dev_priv->rps.pm_iir = 0;
> > - I915_WRITE(GEN6_PMIMR, I915_READ(GEN6_PMIMR) & ~GEN6_PM_RPS_EVENTS);
> > - I915_WRITE(GEN6_PMIIR, GEN6_PM_RPS_EVENTS);
> > - spin_unlock_irq(&dev_priv->irq_lock);
> > - /* unmask all PM interrupts */
> > - I915_WRITE(GEN6_PMINTRMSK, 0);
> > + gen6_enable_rps_interrupts(dev);
> >
> > rc6vids = 0;
> > ret = sandybridge_pcode_read(dev_priv, GEN6_PCODE_READ_RC6VIDS, &rc6vids);
> > @@ -3597,12 +3601,7 @@ static void valleyview_enable_rps(struct drm_device *dev)
> >
> > valleyview_set_rps(dev_priv->dev, dev_priv->rps.rpe_delay);
> >
> > - spin_lock_irq(&dev_priv->irq_lock);
> > - WARN_ON(dev_priv->rps.pm_iir != 0);
> > - I915_WRITE(GEN6_PMIMR, 0);
> > - spin_unlock_irq(&dev_priv->irq_lock);
> > - /* enable all PM interrupts */
> > - I915_WRITE(GEN6_PMINTRMSK, 0);
> > + gen6_enable_rps_interrupts(dev);
> >
> > gen6_gt_force_wake_put(dev_priv);
> > }
> > --
> > 1.8.1.4
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
>
>
> --
> Paulo Zanoni
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-07-11 6:20 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 21:35 [PATCH 00/14] irq locking review v2 Daniel Vetter
2013-07-04 21:35 ` [PATCH 01/14] drm/i915: extract ibx_display_interrupt_update Daniel Vetter
2013-07-08 14:38 ` Paulo Zanoni
2013-07-09 15:21 ` Daniel Vetter
2013-07-04 21:35 ` [PATCH 02/14] drm/i915: improve SERR_INT clearing for fifo underrun reporting Daniel Vetter
2013-07-08 16:46 ` Paulo Zanoni
2013-07-09 20:58 ` [PATCH] " Daniel Vetter
2013-07-09 22:26 ` Paulo Zanoni
2013-07-10 6:30 ` Daniel Vetter
2013-07-10 19:45 ` Paulo Zanoni
2013-07-04 21:35 ` [PATCH 03/14] drm/i915: improve GEN7_ERR_INT " Daniel Vetter
2013-07-09 20:59 ` [PATCH] " Daniel Vetter
2013-07-10 19:47 ` Paulo Zanoni
2013-07-10 20:22 ` Daniel Vetter
2013-07-04 21:35 ` [PATCH 04/14] drm/i915: kill lpt pch transcoder->crtc mapping code for fifo underruns Daniel Vetter
2013-07-08 16:54 ` Paulo Zanoni
2013-07-04 21:35 ` [PATCH 05/14] drm/i915: irq handlers don't need interrupt-safe spinlocks Daniel Vetter
2013-07-04 21:35 ` [PATCH 06/14] drm/i915: streamline hsw_pm_irq_handler Daniel Vetter
2013-07-04 21:35 ` [PATCH 07/14] drm/i915: queue work outside spinlock in hsw_pm_irq_handler Daniel Vetter
2013-07-04 21:35 ` [PATCH 08/14] drm/i915: kill dev_priv->rps.lock Daniel Vetter
2013-07-04 21:35 ` [PATCH 09/14] drm/i915: unify ring irq refcounts (again) Daniel Vetter
2013-07-04 21:35 ` [PATCH 10/14] drm/i915: don't enable PM_VEBOX_CS_ERROR_INTERRUPT Daniel Vetter
2013-07-11 12:37 ` Daniel Vetter
2013-07-04 21:35 ` [PATCH 11/14] drm/i915: unify PM interrupt preinstall sequence Daniel Vetter
2013-07-08 17:06 ` Paulo Zanoni
2013-07-09 15:55 ` Daniel Vetter
2013-07-09 21:00 ` [PATCH] " Daniel Vetter
2013-07-10 20:05 ` Paulo Zanoni
2013-07-10 20:21 ` Daniel Vetter
2013-07-10 20:52 ` Paulo Zanoni
2013-07-04 21:35 ` [PATCH 12/14] drm/i915: unify GT/PM irq postinstall code Daniel Vetter
2013-07-10 20:48 ` Paulo Zanoni
2013-07-11 6:13 ` Daniel Vetter
2013-07-12 20:43 ` [PATCH 1/3] drm/i915: unify PM interrupt preinstall sequence Daniel Vetter
2013-07-12 20:43 ` [PATCH 2/3] drm/i915: unify GT/PM irq postinstall code Daniel Vetter
2013-07-14 20:55 ` Ben Widawsky
2013-07-14 21:31 ` Daniel Vetter
2013-07-14 21:40 ` Ben Widawsky
2013-07-15 0:13 ` Ben Widawsky
2013-07-16 6:17 ` Daniel Vetter
2013-07-12 20:43 ` [PATCH 3/3] drm/i915: extract rps interrupt enable/disable helpers Daniel Vetter
2013-07-14 21:06 ` Ben Widawsky
2013-07-14 21:35 ` Daniel Vetter
2013-07-15 16:39 ` Ben Widawsky
2013-07-14 20:43 ` [PATCH 1/3] drm/i915: unify PM interrupt preinstall sequence Ben Widawsky
2013-07-04 21:35 ` [PATCH 13/14] drm/i915: extract rps interrupt enable/disable helpers Daniel Vetter
2013-07-10 21:12 ` Paulo Zanoni
2013-07-11 6:20 ` Daniel Vetter [this message]
2013-07-04 21:35 ` [PATCH 14/14] drm/i915: simplify rps interrupt enabling/disabling sequence Daniel Vetter
2013-07-16 6:19 ` Daniel Vetter
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=20130711062046.GL6143@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=przanoni@gmail.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