public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Deepak S <deepak.s@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Remove wait for for punit to updates freq.
Date: Wed, 29 Apr 2015 13:26:30 +0300	[thread overview]
Message-ID: <20150429102630.GR18908@intel.com> (raw)
In-Reply-To: <554046EC.5090602@linux.intel.com>

On Wed, Apr 29, 2015 at 08:20:20AM +0530, Deepak S wrote:
> 
> 
> On Wednesday 29 April 2015 12:02 AM, Ville Syrjälä wrote:
> > On Tue, Apr 28, 2015 at 11:16:29AM -0700, Jesse Barnes wrote:
> >> On 03/04/2015 08:08 PM, deepak.s@linux.intel.com wrote:
> >>> From: Deepak S <deepak.s@linux.intel.com>
> >>>
> >>> When GPU is idle on VLV, Request freq to punit should be good enough to
> >>> get the voltage back to VNN. Also, make sure gfx clock force applies
> >>> before requesting the freq fot vlv.
> >>>
> >>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=75244
> >>> suggested-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> >>> Signed-off-by: Deepak S <deepak.s@linux.intel.com>
> >>> ---
> >>>   drivers/gpu/drm/i915/intel_pm.c | 20 ++++----------------
> >>>   1 file changed, 4 insertions(+), 16 deletions(-)
> >>>
> >>> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> >>> index e710b43..2e1ed07 100644
> >>> --- a/drivers/gpu/drm/i915/intel_pm.c
> >>> +++ b/drivers/gpu/drm/i915/intel_pm.c
> >>> @@ -3894,7 +3894,7 @@ static void valleyview_set_rps(struct drm_device *dev, u8 val)
> >>>    * * If Gfx is Idle, then
> >>>    * 1. Mask Turbo interrupts
> >>>    * 2. Bring up Gfx clock
> >>> - * 3. Change the freq to Rpn and wait till P-Unit updates freq
> >>> + * 3. Request the freq to Rpn.
> >>>    * 4. Clear the Force GFX CLK ON bit so that Gfx can down
> >>>    * 5. Unmask Turbo interrupts
> >>>   */
> >>> @@ -3902,8 +3902,8 @@ static void vlv_set_rps_idle(struct drm_i915_private *dev_priv)
> >>>   {
> >>>   	struct drm_device *dev = dev_priv->dev;
> >>>   
> >>> -	/* CHV and latest VLV don't need to force the gfx clock */
> >>> -	if (IS_CHERRYVIEW(dev) || dev->pdev->revision >= 0xd) {
> >>> +	/* CHV don't need to force the gfx clock */
> >>> +	if (IS_CHERRYVIEW(dev)) {
> >>>   		valleyview_set_rps(dev_priv->dev, dev_priv->rps.min_freq_softlimit);
> >>>   		return;
> >>>   	}
> >>> @@ -3920,20 +3920,8 @@ static void vlv_set_rps_idle(struct drm_i915_private *dev_priv)
> >>>   		   gen6_sanitize_rps_pm_mask(dev_priv, ~0));
> >>>   
> >>>   	vlv_force_gfx_clock(dev_priv, true);
> >>> -
> >>> -	dev_priv->rps.cur_freq = dev_priv->rps.min_freq_softlimit;
> >>> -
> >>> -	vlv_punit_write(dev_priv, PUNIT_REG_GPU_FREQ_REQ,
> >>> -					dev_priv->rps.min_freq_softlimit);
> >>> -
> >>> -	if (wait_for(((vlv_punit_read(dev_priv, PUNIT_REG_GPU_FREQ_STS))
> >>> -				& GENFREQSTATUS) == 0, 100))
> >>> -		DRM_ERROR("timed out waiting for Punit\n");
> >>> -
> >>> +	valleyview_set_rps(dev_priv->dev, dev_priv->rps.min_freq_softlimit);
> >>>   	vlv_force_gfx_clock(dev_priv, false);
> >>> -
> >>> -	I915_WRITE(GEN6_PMINTRMSK,
> >>> -		   gen6_rps_pm_mask(dev_priv, dev_priv->rps.cur_freq));
> >>>   }
> >>>   
> >>>   void gen6_rps_idle(struct drm_i915_private *dev_priv)
> >>>
> >> Yeah I think this is fine (may need a rebase though, you can keep my r-b
> >> if you do that in case Jani doesn't want to deal with the merge conflicts).
> >>
> >> Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> > The removal of the stepping check is still confusing me even if the
> > rest would be OK.
> >
> Stepping check was added latest BYT release. On older BYT stepping, We used to wait for punit to grant the freq in GT Idle case, (most of the cases punit is timing out :( )
> We now make the gfx clock force apply to all VLV and then request the freq to RPn this should be good enough to get voltage to Vnn.

But we shouldn't need the gfx clock force for the latest VLV
stepping(s), and we certainly didn't do it before. So why do
it now?

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-04-29 10:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05  4:08 [PATCH] drm/i915: Remove wait for for punit to updates freq deepak.s
2015-03-05  4:08 ` [PATCH] drm/i915: Update PM interrupts before updating the freq deepak.s
2015-03-05 10:30   ` shuang.he
2015-03-05  7:46 ` [PATCH] drm/i915: Remove wait for for punit to updates freq shuang.he
2015-04-13 11:55 ` Jani Nikula
2015-04-13 12:10   ` Ville Syrjälä
2015-04-28 10:43     ` Deepak S
2015-04-28 18:16 ` Jesse Barnes
2015-04-28 18:32   ` Ville Syrjälä
2015-04-29  2:50     ` Deepak S
2015-04-29 10:26       ` Ville Syrjälä [this message]
2015-04-30 10:04         ` Deepak S
2015-05-04  7:59           ` Daniel Vetter
2015-04-29  2:37   ` 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=20150429102630.GR18908@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=deepak.s@linux.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