From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/3] drm/i915/skl: Restore pipe interrupt registers after power well enabling
Date: Tue, 3 Mar 2015 09:23:24 +0100 [thread overview]
Message-ID: <20150303082324.GH18775@phenom.ffwll.local> (raw)
In-Reply-To: <CA+gsUGR_WUPqjmXvraUHUidzr=w0EHiVHmAQTz85BH+L5A4pxQ@mail.gmail.com>
On Mon, Mar 02, 2015 at 03:37:47PM -0300, Paulo Zanoni wrote:
> 2015-02-13 17:37 GMT-02:00 Damien Lespiau <damien.lespiau@intel.com>:
> > The pipe interrupt registers are in the actual pipe power well, so we
> > need to restore them when re-enable the corresponding power well.
> >
> > I've also copied what we do on HSW/BDW for VGA, even if the we haven't
> > enabled unclaimed registers just yet.
> >
> > Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_irq.c | 4 ++++
> > drivers/gpu/drm/i915/intel_runtime_pm.c | 31 +++++++++++++++++++++++++++++++
> > 2 files changed, 35 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> > index 65fe9e7..292ba89 100644
> > --- a/drivers/gpu/drm/i915/i915_irq.c
> > +++ b/drivers/gpu/drm/i915/i915_irq.c
> > @@ -3235,6 +3235,10 @@ void gen8_irq_power_well_post_enable(struct drm_i915_private *dev_priv,
> > uint32_t extra_ier = GEN8_PIPE_VBLANK | GEN8_PIPE_FIFO_UNDERRUN;
> >
> > spin_lock_irq(&dev_priv->irq_lock);
> > + if (pipe_mask & 1 << PIPE_A)
> > + GEN8_IRQ_INIT_NDX(DE_PIPE, PIPE_A,
> > + dev_priv->de_irq_mask[PIPE_A],
> > + ~dev_priv->de_irq_mask[PIPE_A] | extra_ier);
> > if (pipe_mask & 1 << PIPE_B)
> > GEN8_IRQ_INIT_NDX(DE_PIPE, PIPE_B,
> > dev_priv->de_irq_mask[PIPE_B],
> > diff --git a/drivers/gpu/drm/i915/intel_runtime_pm.c b/drivers/gpu/drm/i915/intel_runtime_pm.c
> > index 35e0cb6..8989747 100644
> > --- a/drivers/gpu/drm/i915/intel_runtime_pm.c
> > +++ b/drivers/gpu/drm/i915/intel_runtime_pm.c
> > @@ -199,6 +199,34 @@ static void hsw_power_well_post_enable(struct drm_i915_private *dev_priv)
> > 1 << PIPE_C | 1 << PIPE_B);
> > }
> >
> > +static void skl_power_well_post_enable(struct drm_i915_private *dev_priv,
> > + struct i915_power_well *power_well)
> > +{
> > + struct drm_device *dev = dev_priv->dev;
> > +
> > + /*
> > + * After we re-enable the power well, if we touch VGA register 0x3d5
> > + * we'll get unclaimed register interrupts. This stops after we write
> > + * anything to the VGA MSR register. The vgacon module uses this
> > + * register all the time, so if we unbind our driver and, as a
> > + * consequence, bind vgacon, we'll get stuck in an infinite loop at
> > + * console_unlock(). So make here we touch the VGA MSR register, making
> > + * sure vgacon can keep working normally without triggering interrupts
> > + * and error messages.
> > + */
> > + if (power_well->data == SKL_DISP_PW_2) {
> > + vga_get_uninterruptible(dev->pdev, VGA_RSRC_LEGACY_IO);
> > + outb(inb(VGA_MSR_READ), VGA_MSR_WRITE);
> > + vga_put(dev->pdev, VGA_RSRC_LEGACY_IO);
> > +
> > + gen8_irq_power_well_post_enable(dev_priv,
> > + 1 << PIPE_C | 1 << PIPE_B);
> > + }
> > +
> > + if (power_well->data == SKL_DISP_PW_1)
> > + gen8_irq_power_well_post_enable(dev_priv, 1 << PIPE_A);
> > +}
> > +
> > static void hsw_set_power_well(struct drm_i915_private *dev_priv,
> > struct i915_power_well *power_well, bool enable)
> > {
> > @@ -359,6 +387,9 @@ static void skl_set_power_well(struct drm_i915_private *dev_priv,
> > DRM_ERROR("PG2 distributing status timeout\n");
> > }
> > }
> > +
> > + if (enable)
> > + skl_power_well_post_enable(dev_priv, power_well);
>
> Please take a look at "drm/i915: only run hsw_power_well_post_enable
> when really needed": http://patchwork.freedesktop.org/patch/34764/ and
> please do the equivalent change here. I also won't complain if you
> create "is_enabled" and "enable_requested" variables on
> skl_set_power_well, just like we have for hsw_set_power_well.
tbh I wonder whether we should move the irq enable/disable into the crtc
enable/disable functions on gen8+. That would have avoided the "have we
enabled this already" logic, which tends to be fragile in general. Otoh
this works too.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-03 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 19:37 [PATCH 0/3] Restore pipe interrupts registers after power well enabling Damien Lespiau
2015-02-13 19:37 ` [PATCH 1/3] drm/i915/skl: Make gen8_irq_power_well_post_enable() take a pipe mask Damien Lespiau
2015-03-02 18:32 ` Paulo Zanoni
2015-02-13 19:37 ` [PATCH 2/3] drm/i915/skl: Restore pipe interrupt registers after power well enabling Damien Lespiau
2015-03-02 18:37 ` Paulo Zanoni
2015-03-03 8:23 ` Daniel Vetter [this message]
2015-02-13 19:37 ` [PATCH 3/3] drm/i915: Remove unused condition in hsw_power_well_post_enable() Damien Lespiau
2015-02-14 7:04 ` shuang.he
2015-03-02 18:38 ` Paulo Zanoni
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=20150303082324.GH18775@phenom.ffwll.local \
--to=daniel@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