From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: Deepak S <deepak.s@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/6] drm/i915: Bring UP Power Wells before disabling RC6.
Date: Tue, 8 Apr 2014 15:43:32 +0300 [thread overview]
Message-ID: <20140408124332.GH4481@intel.com> (raw)
In-Reply-To: <20140407213620.GA19665@bwidawsk.net>
On Mon, Apr 07, 2014 at 02:36:20PM -0700, Ben Widawsky wrote:
> On Mon, Apr 07, 2014 at 05:01:46PM -0300, Rodrigo Vivi wrote:
> > From: Deepak S <deepak.s@intel.com>
> >
> > We need do forcewake before Disabling RC6, This is what the BIOS
> > expects while going into suspend.
> >
> > v2: updated commit message. (Daniel)
> >
> > Signed-off-by: Deepak S <deepak.s@intel.com>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@gmail.com>
> > ---
> > drivers/gpu/drm/i915/intel_pm.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > index 04af065..ad2ff99 100644
> > --- a/drivers/gpu/drm/i915/intel_pm.c
> > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > @@ -3198,8 +3198,14 @@ static void valleyview_disable_rps(struct drm_device *dev)
> > {
> > struct drm_i915_private *dev_priv = dev->dev_private;
> >
> > + /* we're doing forcewake before Disabling RC6,
> > + * This what the BIOS expects when going into suspend */
> > + gen6_gt_force_wake_get(dev_priv, FORCEWAKE_ALL);
> > +
> > I915_WRITE(GEN6_RC_CONTROL, 0);
> >
> > + gen6_gt_force_wake_put(dev_priv, FORCEWAKE_ALL);
> > +
> > gen6_disable_rps_interrupts(dev);
> > }
> >
>
> Isn't the forcewake done as part of I915_WRITE sufficient?
Writes don't do forcewake, nor is the register even part of the
VLV forcewake ranges.
I guess the rationale for this patche is still a bit vague. But if it's
really needed, I wonder whether we should do this same dance for !VLV
too? Do we have any "GPU stuck in wrong power state after suspend" type of
bugs still around?
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-04-08 12:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 20:01 [PATCH 0/6] drm-intel-collector - update Rodrigo Vivi
2014-04-07 20:01 ` [PATCH 1/6] drm/i915: Bring UP Power Wells before disabling RC6 Rodrigo Vivi
2014-04-07 21:36 ` Ben Widawsky
2014-04-08 12:43 ` Ville Syrjälä [this message]
2014-04-08 12:52 ` S, Deepak
2014-04-09 4:13 ` Ben Widawsky
2014-04-09 4:21 ` S, Deepak
2014-04-09 13:02 ` Daniel Vetter
2014-04-09 19:15 ` Deepak S
2014-04-09 21:46 ` Ben Widawsky
2014-04-07 20:01 ` [PATCH 2/6] drm/i915: dma_buf_vunmap is presumed not to fail, don't let it Rodrigo Vivi
2014-04-09 13:03 ` Daniel Vetter
2014-04-07 20:01 ` [PATCH 3/6] drm/i915: Add support for stealing purgable stolen pages Rodrigo Vivi
2014-04-08 4:32 ` Gupta, Sourab
2014-04-08 6:45 ` Chris Wilson
2014-04-08 6:53 ` Gupta, Sourab
2014-04-09 13:06 ` Daniel Vetter
2014-04-10 10:12 ` Gupta, Sourab
2014-04-11 8:55 ` Daniel Vetter
2014-04-14 9:53 ` Gupta, Sourab
2014-04-07 20:01 ` [PATCH 4/6] drm/i915: add flag to prevent dmesg spam on context banning Rodrigo Vivi
2014-04-08 14:04 ` Mika Kuoppala
2014-04-07 20:01 ` [PATCH 5/6] drm/i915: Do not allow a pending forcewake put to unbalance across reset Rodrigo Vivi
2014-04-07 20:01 ` [PATCH 6/6] drm/i915: Don't save/restore RS when not used Rodrigo Vivi
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=20140408124332.GH4481@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=ben@bwidawsk.net \
--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