public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Keith Packard" <keithp@keithp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Dave Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: [PULL] drm-intel-fixes (drm/i915 driver)
Date: Tue, 12 Jul 2011 10:58:03 -0700	[thread overview]
Message-ID: <yun7h7ne5zo.fsf@aiko.keithp.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]


What have we got here: 

 * A list of DP fixes from Jesse to make the code conform more closely
   to the specification.

 * Making Ivybridge use the Sandybridge GPU reset path.

 * Recover from i915 load failure without causing a later panic
   when the shrinker ran.

 * Revert the RC6 enable patch -- there are at least two machines which
   mysteriously fail with RC6 enabled. We found lots of possible causes,
   none of which appear to help these last few hold-outs.

 * Fix an obvious typo -- the GPU idling code was using the wrong variable
   for the size of the ring. This may well cause spurious suspend
   failures as the GPU wouldn't have been reliably idled.

The following changes since commit fe0d42203cb5616eeff68b14576a0f7e2dd56625:

  Linux 3.0-rc6 (2011-07-04 15:56:24 -0700)

are available in the git repository at:
  ssh://master.kernel.org/pub/scm/linux/kernel/git/keithp/linux-2.6.git drm-intel-fixes

Chris Wilson (1):
      drm/i915/ringbuffer: Idling requires waiting for the ring to be empty

Jesse Barnes (7):
      drm/i915/dp: retry link status read 3 times on failure
      drm/i915/dp: use DP DPCD defines when looking at DPCD values
      drm/i915/dp: read more receiver capability bits on hotplug
      drm/i915/dp: try to read receiver capabilities 3 times when detecting
      drm/i915/dp: remove DPMS mode tracking from DP
      drm/i915/dp: consolidate AUX retry code
      drm/i915/dp: manage sink power state if possible

Keith Packard (2):
      drm/i915: Clean up i915_driver_load failure path
      Revert "drm/i915: enable rc6 by default"

Kenneth Graunke (1):
      drm/i915: Enable GPU reset on Ivybridge.

 drivers/gpu/drm/i915/i915_dma.c         |   14 +++-
 drivers/gpu/drm/i915/i915_drv.c         |    3 +-
 drivers/gpu/drm/i915/intel_dp.c         |  118 ++++++++++++++++++++++++-------
 drivers/gpu/drm/i915/intel_ringbuffer.h |    2 +-
 4 files changed, 105 insertions(+), 32 deletions(-)


-- 
keith.packard@intel.com

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2011-07-12 17:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 17:58 Keith Packard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-12-16 17:39 [PULL] drm-intel-fixes (drm/i915 driver) Keith Packard
2011-09-30  1:18 Keith Packard
2011-10-06 17:12 ` Linus Torvalds
2011-10-06 21:03   ` Keith Packard
2011-10-06 23:02     ` Woody Suwalski
2011-08-15 19:30 Keith Packard
2011-07-21 16:42 Keith Packard
2011-07-01 23:04 Keith Packard
2011-06-28 17:28 Keith Packard
2011-06-25  4:11 Keith Packard

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=yun7h7ne5zo.fsf@aiko.keithp.com \
    --to=keithp@keithp.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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