From: Ben Widawsky <ben@bwidawsk.net>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: intel-gfx@lists.freedesktop.org,
Art Runyan <arthur.j.runyan@intel.com>,
Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 1/6] drm/i915: grab force_wake when restoring LCPLL
Date: Mon, 19 Aug 2013 15:53:11 -0700 [thread overview]
Message-ID: <20130819225310.GB1059@bwidawsk.net> (raw)
In-Reply-To: <1376938873-3692-1-git-send-email-przanoni@gmail.com>
On Mon, Aug 19, 2013 at 04:01:13PM -0300, Paulo Zanoni wrote:
> From: Paulo Zanoni <paulo.r.zanoni@intel.com>
>
> If LCPLL is disabled, there's a chance we might be in package C8 state
> or deeper, and we'll get a hard hang when restoring LCPLL (also, a red
> led lights up on my motherboard). So grab the force_wake, which will
> get us out of RC6 and, as a consequence, out of PC8+ (since we need
> RC6 to get into PC8+).
>
> v2: Call the correct force_wake interface.
>
> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Hi Paulo. As I recall, the steps in the bspec are laid out exactly so we
don't have to call forcewake. I think the explanation sounds a little
fishy.
Specifically, I thought D_COMP COMP_FORCE + waiting for PLL lock was
sufficient. If it's not, I worry you're papering over another bug, or
incorrect bspec sequence.
Not opposed to the patch in the meanwhile, but it just feels a little
unsafe to me.
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-08-19 22:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 16:18 [PATCH 0/6] Final PC8+ patches Paulo Zanoni
2013-08-19 16:18 ` [PATCH 1/6] drm/i915: grab force_wake when restoring LCPLL Paulo Zanoni
2013-08-19 18:25 ` Chris Wilson
2013-08-19 19:01 ` Paulo Zanoni
2013-08-19 22:53 ` Ben Widawsky [this message]
2013-08-20 14:27 ` Paulo Zanoni
2013-08-19 16:18 ` [PATCH 2/6] drm/i915: fix SDEIMR assertion when disabling LCPLL Paulo Zanoni
2013-08-21 15:37 ` Rodrigo Vivi
2013-08-19 16:18 ` [PATCH 3/6] drm/i915: allow package C8+ states on Haswell (disabled) Paulo Zanoni
2013-08-19 18:29 ` Chris Wilson
2013-08-19 16:18 ` [PATCH 4/6] drm/i915: add i915_pc8_status debugfs file Paulo Zanoni
2013-08-21 15:42 ` Rodrigo Vivi
2013-08-19 16:18 ` [PATCH 5/6] drm/i915: add i915.pc8_timeout function Paulo Zanoni
2013-08-21 15:43 ` Rodrigo Vivi
2013-08-19 16:18 ` [PATCH 6/6] drm/i915: enable Package C8+ by default Paulo Zanoni
2013-08-21 15:43 ` Rodrigo Vivi
2013-08-22 14:13 ` Daniel Vetter
2013-08-19 16:20 ` [PATCH igt] tests: add pc8 Paulo Zanoni
2013-08-20 20:18 ` 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=20130819225310.GB1059@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=arthur.j.runyan@intel.com \
--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