From: Paulo Zanoni <przanoni@gmail.com>
To: intel-gfx@lists.freedesktop.org
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: [PATCH 0/3] BDW runtime PM fixes
Date: Tue, 1 Apr 2014 19:39:46 -0300 [thread overview]
Message-ID: <1396391989-2244-1-git-send-email-przanoni@gmail.com> (raw)
From: Paulo Zanoni <paulo.r.zanoni@intel.com>
Hi
I got a little surprised to see the BDW patches merged so fast, I thought I was
going to have time to resend the last series with these last patches in.
The first patch replaces a HSW-specific WARN that was happening all the time on
BDW with a gen-agnostic WARN. The second patch is just a debugfs fix. The third
patch fixes an infinite loop, but it does not fix the undelying reason why the
infinite loop happens, so maybe we don't want to merge it so we don't hide the
real bug.
With these last patches on top of -nightly, my BDW machine passes pm_pc8 without
errors.
Thanks,
Paulo
Paulo Zanoni (2):
drm/i915: only check for irqs_disabled when disabling LCPLL
drm/i915: fix infinite loop at gen6_update_ring_freq
Zhenyu Wang (1):
drm/i915: Allow i915_pc8_status debug info on BDW
drivers/gpu/drm/i915/i915_debugfs.c | 2 +-
drivers/gpu/drm/i915/intel_display.c | 17 +++++++----------
drivers/gpu/drm/i915/intel_pm.c | 3 ++-
3 files changed, 10 insertions(+), 12 deletions(-)
--
1.8.5.3
next reply other threads:[~2014-04-01 22:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 22:39 Paulo Zanoni [this message]
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
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=1396391989-2244-1-git-send-email-przanoni@gmail.com \
--to=przanoni@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.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