From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 1/3] drm/i915: only check for irqs_disabled when disabling LCPLL
Date: Wed, 2 Apr 2014 09:28:06 +0200 [thread overview]
Message-ID: <20140402072806.GO7225@phenom.ffwll.local> (raw)
In-Reply-To: <1396391989-2244-2-git-send-email-przanoni@gmail.com>
On Tue, Apr 01, 2014 at 07:39:47PM -0300, Paulo Zanoni wrote:
> From: Paulo Zanoni <paulo.r.zanoni@intel.com>
>
> Because if we keep the current code, we'll get tons of WARNs on
> Broadwell, since the code is Haswell-specific.
>
> We could have also added a Broadwell-specific code there, but it's not
> really needed since we never disable LCPLL with the hotplug interrupts
> still enabled. So keep the easy-and-simple-to-maintain solution until
> we actually need something else.
>
> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
I'll see how quickly QA reports this before merging it. If you spot the
bug please reply with the Bugzilla: tag, thanks.
-Daniel
> ---
> drivers/gpu/drm/i915/intel_display.c | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 3fb3bd3..6691970 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -6861,8 +6861,6 @@ static void assert_can_disable_lcpll(struct drm_i915_private *dev_priv)
> struct drm_device *dev = dev_priv->dev;
> struct intel_ddi_plls *plls = &dev_priv->ddi_plls;
> struct intel_crtc *crtc;
> - unsigned long irqflags;
> - uint32_t val;
>
> list_for_each_entry(crtc, &dev->mode_config.crtc_list, base.head)
> WARN(crtc->active, "CRTC for pipe %c enabled\n",
> @@ -6883,14 +6881,13 @@ static void assert_can_disable_lcpll(struct drm_i915_private *dev_priv)
> "Utility pin enabled\n");
> WARN(I915_READ(PCH_GTC_CTL) & PCH_GTC_ENABLE, "PCH GTC enabled\n");
>
> - spin_lock_irqsave(&dev_priv->irq_lock, irqflags);
> - val = I915_READ(DEIMR);
> - WARN((val | DE_PCH_EVENT_IVB) != 0xffffffff,
> - "Unexpected DEIMR bits enabled: 0x%x\n", val);
> - val = I915_READ(SDEIMR);
> - WARN((val | SDE_HOTPLUG_MASK_CPT) != 0xffffffff,
> - "Unexpected SDEIMR bits enabled: 0x%x\n", val);
> - spin_unlock_irqrestore(&dev_priv->irq_lock, irqflags);
> + /*
> + * In theory we can still leave IRQs enabled, as long as only the HPD
> + * interrupts remain enabled. We used to check for that, but since it's
> + * gen-specific and since we only disable LCPLL after we fully disable
> + * the interrupts, the check below should be enough.
> + */
> + WARN(!dev_priv->pm.irqs_disabled, "IRQs enabled\n");
> }
>
> static void hsw_write_dcomp(struct drm_i915_private *dev_priv, uint32_t val)
> --
> 1.8.5.3
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-04-02 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 22:39 [PATCH 0/3] BDW runtime PM fixes Paulo Zanoni
2014-04-01 22:39 ` [PATCH 1/3] drm/i915: only check for irqs_disabled when disabling LCPLL Paulo Zanoni
2014-04-02 7:28 ` Daniel Vetter [this message]
2014-04-01 22:39 ` [PATCH 2/3] drm/i915: Allow i915_pc8_status debug info on BDW Paulo Zanoni
2014-04-02 5:04 ` Ben Widawsky
2014-04-02 7:27 ` Daniel Vetter
2014-04-01 22:39 ` [PATCH 3/3] drm/i915: fix infinite loop at gen6_update_ring_freq Paulo Zanoni
2014-04-02 5:03 ` Ben Widawsky
2014-04-02 7:26 ` Daniel Vetter
2014-04-02 14:58 ` [PATCH 0/3] BDW runtime PM fixes 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=20140402072806.GO7225@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--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