All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 12/16] drm/i915: treat Ivy Bridge watermarks like Sandy Bridge
Date: Tue, 26 Apr 2011 16:38:50 -0700	[thread overview]
Message-ID: <1303861134-8762-13-git-send-email-jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <1303861134-8762-1-git-send-email-jbarnes@virtuousgeek.org>

Not fully tested.

Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
---
 drivers/gpu/drm/i915/intel_display.c |    9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletions(-)

diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index 866abe5..908c4d9 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -7229,7 +7229,7 @@ void intel_enable_clock_gating(struct drm_device *dev)
 				   _3D_CHICKEN2_WM_READ_PIPELINED);
 		}
 
-		if (IS_GEN6(dev)) {
+		if (IS_GEN6(dev) || IS_IVYBRIDGE(dev)) {
 			I915_WRITE(WM3_LP_ILK, 0);
 			I915_WRITE(WM2_LP_ILK, 0);
 			I915_WRITE(WM1_LP_ILK, 0);
@@ -7491,6 +7491,13 @@ static void intel_init_display(struct drm_device *dev)
 				dev_priv->display.train_fdi = ivb_fdi_link_train;
 			else
 				dev_priv->display.train_fdi = ivb_manual_fdi_link_train;
+			if (SNB_READ_WM0_LATENCY()) {
+				dev_priv->display.update_wm = sandybridge_update_wm;
+			} else {
+				DRM_DEBUG_KMS("Failed to read display plane latency. "
+					      "Disable CxSR\n");
+				dev_priv->display.update_wm = NULL;
+			}
 		} else
 			dev_priv->display.update_wm = NULL;
 	} else if (IS_PINEVIEW(dev)) {
-- 
1.7.4.1

  parent reply	other threads:[~2011-04-26 23:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26 23:38 Initial Ivy Bridge support Jesse Barnes
2011-04-26 23:38 ` [PATCH 01/16] drm/i915: make FDI training a display function Jesse Barnes
2011-04-27 15:58   ` Ben Widawsky
2011-04-27 20:51     ` Jesse Barnes
2011-04-26 23:38 ` [PATCH 02/16] drm/i915: split irq handling into per-chipset functions Jesse Barnes
2011-04-26 23:38 ` [PATCH 03/16] drm/i915: split enable/disable vblank code into chipset specific functions Jesse Barnes
2011-04-26 23:38 ` [PATCH 04/16] drm/i915: add Ivy Bridge PCI IDs and flags Jesse Barnes
2011-04-27  6:59   ` Chris Wilson
2011-04-27 21:01     ` Jesse Barnes
2011-04-27 21:28       ` Chris Wilson
2011-04-27  7:23   ` Chris Wilson
2011-04-27 21:02     ` Jesse Barnes
2011-04-26 23:38 ` [PATCH 05/16] drm/i915: add IS_GEN7 macro to cover Ivy Bridge and later Jesse Barnes
2011-04-26 23:38 ` [PATCH 06/16] agp/intel: add Ivy Bridge support Jesse Barnes
2011-04-26 23:38 ` [PATCH 07/16] drm/i915: add PantherPoint PCH ID Jesse Barnes
2011-04-27 15:05   ` Keith Packard
2011-04-27 21:13     ` Jesse Barnes
2011-04-26 23:38 ` [PATCH 08/16] drm/i915: Ivy Bridge has split display and pipe control Jesse Barnes
2011-04-27  7:19   ` Chris Wilson
2011-04-27 20:02     ` Daniel Vetter
2011-04-27 21:03     ` Jesse Barnes
2011-04-26 23:38 ` [PATCH 09/16] drm/i915: add swizzle/tiling support for Ivy Bridge Jesse Barnes
2011-04-26 23:38 ` [PATCH 10/16] drm/i915: automatic FDI training " Jesse Barnes
2011-04-26 23:38 ` [PATCH 11/16] drm/i915: manual FDI training " Jesse Barnes
2011-04-27 15:10   ` Keith Packard
2011-04-27 21:13     ` Jesse Barnes
2011-04-26 23:38 ` Jesse Barnes [this message]
2011-04-26 23:38 ` [PATCH 13/16] drm/i915: interrupt & vblank support " Jesse Barnes
2011-04-26 23:38 ` [PATCH 14/16] drm/i915: page flip " Jesse Barnes
2011-04-26 23:38 ` [PATCH 15/16] drm/i915: untested DP " Jesse Barnes
2011-04-26 23:38 ` [PATCH 16/16] drm/i915: ring " Jesse Barnes
2011-04-26 23:52 ` Initial Ivy Bridge support Jesse Barnes

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=1303861134-8762-13-git-send-email-jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.