From: Paulo Zanoni <przanoni@gmail.com>
To: intel-gfx@lists.freedesktop.org
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: [PATCH 0/4] PC8 fixes
Date: Wed, 30 Oct 2013 19:40:22 -0200 [thread overview]
Message-ID: <1383169226-16707-1-git-send-email-przanoni@gmail.com> (raw)
From: Paulo Zanoni <paulo.r.zanoni@intel.com>
Hi
Patch 1 was sent by Chris a few weeks ago, and patch 2 is my bikeshed to his
original patch. They shouldn't fix any particular bug, and patch 2 will WARN in
case we hit the bug that should not happen.
Patches 3 and 4 fix problems that I discovered while working on the runtime D3.
Since these bugs affect PC8 even without D3, I think they should be merged
before D3. I already have subtests for these problems on the pc8 test, so we
should be fine.
Thanks,
Paulo
Chris Wilson (1):
drm/i915: Do not enable package C8 on unsupported hardware
Paulo Zanoni (3):
drm/i915: WARN if !HAS_PC8 when enabling/disabling PC8
drm/i915: get a PC8 reference when enabling the power well
drm/i915: get/put PC8 when we get/put a CRTC
drivers/gpu/drm/i915/i915_drv.h | 1 +
drivers/gpu/drm/i915/intel_display.c | 48 +++++++++++++++++++++++++++++++++---
drivers/gpu/drm/i915/intel_pm.c | 14 +++++++++--
3 files changed, 57 insertions(+), 6 deletions(-)
--
1.8.3.1
next reply other threads:[~2013-10-30 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 21:40 Paulo Zanoni [this message]
2013-10-30 21:40 ` [PATCH 1/4] drm/i915: Do not enable package C8 on unsupported hardware Paulo Zanoni
2013-10-30 21:40 ` [PATCH 2/4] drm/i915: WARN if !HAS_PC8 when enabling/disabling PC8 Paulo Zanoni
2013-10-30 21:40 ` [PATCH 3/4] drm/i915: get a PC8 reference when enabling the power well Paulo Zanoni
2013-10-31 12:40 ` Imre Deak
2013-10-31 16:00 ` Paulo Zanoni
2013-10-30 21:40 ` [PATCH 4/4] drm/i915: get/put PC8 when we get/put a CRTC Paulo Zanoni
2013-11-01 15:49 ` Paulo Zanoni
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=1383169226-16707-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;
as well as URLs for NNTP newsgroup(s).