From: Deepak S <deepak.s@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Deepak S <deepak.s@intel.com>
Subject: Re: [PATCH 3/3] drm/i915: Mask PM interrupt generation when at up/down limits
Date: Thu, 27 Mar 2014 20:21:29 +0530 [thread overview]
Message-ID: <53343AF1.20906@linux.intel.com> (raw)
In-Reply-To: <1395908661-7355-3-git-send-email-chris@chris-wilson.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 3109 bytes --]
On Thursday 27 March 2014 01:54 PM, Chris Wilson wrote:
> The speculation is that we can conserve more power by masking off the
> interrupts at source (PMINTRMSK) rather than filtering them by the
> up/down thresholds (RPINTLIM).
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Deepak S <deepak.s@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_pm.c | 32 ++++++++++++++++++++------------
> 1 file changed, 20 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> index 3ad590924062..0a76e9baeca2 100644
> --- a/drivers/gpu/drm/i915/intel_pm.c
> +++ b/drivers/gpu/drm/i915/intel_pm.c
> @@ -3006,6 +3006,25 @@ static void gen6_set_rps_thresholds(struct drm_i915_private *dev_priv, u8 val)
> dev_priv->rps.last_adj = 0;
> }
>
> +static u32 gen6_rps_pm_mask(struct drm_i915_private *dev_priv, u8 val)
> +{
> + u32 mask;
> +
> + mask = GEN6_PM_RP_DOWN_TIMEOUT;
> + if (val > dev_priv->rps.min_freq_softlimit)
> + mask |= GEN6_PM_RP_DOWN_THRESHOLD;
> + if (val < dev_priv->rps.max_freq_softlimit)
> + mask |= GEN6_PM_RP_UP_THRESHOLD;
> +
> + /* IVB and SNB hard hangs on looping batchbuffer
> + * if GEN6_PM_UP_EI_EXPIRED is masked.
> + */
> + if (INTEL_INFO(dev_priv->dev)->gen <= 7 && !IS_HASWELL(dev_priv->dev))
> + mask |= GEN6_PM_RP_UP_EI_EXPIRED;
> +
> + return ~mask;
> +}
> +
> /* gen6_set_rps is called to update the frequency request, but should also be
> * called when the range (min_delay and max_delay) is modified so that we can
> * update the GEN6_RP_INTERRUPT_LIMITS register accordingly. */
> @@ -3037,6 +3056,7 @@ void gen6_set_rps(struct drm_device *dev, u8 val)
> * until we hit the minimum or maximum frequencies.
> */
> I915_WRITE(GEN6_RP_INTERRUPT_LIMITS, gen6_rps_limits(dev_priv, val));
> + I915_WRITE(GEN6_PMINTRMSK, gen6_rps_pm_mask(dev_priv, val));
>
> POSTING_READ(GEN6_RPNSWREQ);
>
> @@ -3220,24 +3240,12 @@ int intel_enable_rc6(const struct drm_device *dev)
> static void gen6_enable_rps_interrupts(struct drm_device *dev)
> {
> struct drm_i915_private *dev_priv = dev->dev_private;
> - u32 enabled_intrs;
>
> spin_lock_irq(&dev_priv->irq_lock);
> WARN_ON(dev_priv->rps.pm_iir);
> snb_enable_pm_irq(dev_priv, dev_priv->pm_rps_events);
> I915_WRITE(GEN6_PMIIR, dev_priv->pm_rps_events);
> spin_unlock_irq(&dev_priv->irq_lock);
> -
> - /* only unmask PM interrupts we need. Mask all others. */
> - enabled_intrs = dev_priv->pm_rps_events;
> -
> - /* IVB and SNB hard hangs on looping batchbuffer
> - * if GEN6_PM_UP_EI_EXPIRED is masked.
> - */
> - if (INTEL_INFO(dev)->gen <= 7 && !IS_HASWELL(dev))
> - enabled_intrs |= GEN6_PM_RP_UP_EI_EXPIRED;
> -
> - I915_WRITE(GEN6_PMINTRMSK, ~enabled_intrs);
> }
>
> static void gen8_enable_rps(struct drm_device *dev)
On VLV, gen6_enable_rps_interrupts is used to enable turbo
interrutpts. I think we need to extend gen6_rps_pm_maskto valleyview also?
[-- Attachment #1.2: Type: text/html, Size: 3703 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-03-27 14:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 8:24 [PATCH 1/3] Revert "drm/i915: Disable/Enable PM Intrrupts based on the current freq." Chris Wilson
2014-03-27 8:24 ` [PATCH 2/3] drm/i915: Refactor gen6_set_rps Chris Wilson
2014-03-30 6:45 ` Deepak S
2014-03-27 8:24 ` [PATCH 3/3] drm/i915: Mask PM interrupt generation when at up/down limits Chris Wilson
2014-03-27 8:34 ` Chris Wilson
2014-03-27 8:35 ` [PATCH] drm/i915: Mask PM interrupt generation when at up/down limits for VLV Chris Wilson
2014-03-27 8:46 ` Chris Wilson
2014-03-27 14:51 ` Deepak S [this message]
2014-03-27 15:26 ` [PATCH 3/3] drm/i915: Mask PM interrupt generation when at up/down limits Chris Wilson
2014-03-28 8:03 ` [PATCH] drm/i915: Mask PM/RPS interrupt generation based on activity Chris Wilson
2014-03-30 6:38 ` Deepak S
2014-03-31 8:30 ` Daniel Vetter
2014-03-30 6:48 ` [PATCH 1/3] Revert "drm/i915: Disable/Enable PM Intrrupts based on the current freq." Deepak S
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=53343AF1.20906@linux.intel.com \
--to=deepak.s@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=deepak.s@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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