From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Eric Anholt <eric@anholt.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.32 regression (bisected): Video tearing/glitching with T400 laptops
Date: Thu, 8 Oct 2009 10:36:20 -0700 [thread overview]
Message-ID: <20091008103620.5e5aae66@jbarnes-g45> (raw)
In-Reply-To: <E1Mtqnb-0002x7-TJ@closure.thunk.org>
On Fri, 02 Oct 2009 18:40:27 -0400
"Theodore Ts'o" <tytso@mit.edu> wrote:
> Hi,
>
> In recent kernels, my X display (running with a KMS-enabled X server)
> has been very jittery and with lots of glitching and tearing --- sorry
> if this isn't the correct technical term, not sure what it is --- on
> my T400 Lenovo laptop. It seems related to what is on the desktop,
> and moving the mouse does seem to affect the rate and percentage of
> the screen which jitters --- which is enough to be very distracting,
> although I can still read the contents of the windows where the screen
> is tearing/glitching/flashing.
>
> I bisected it down to this commit:
Can you give this patch a try? It seems to work for Keith at least,
and it sounds like he was seeing the same problem.
--
Jesse Barnes, Intel Open Source Technology Center
diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
index 0466ddb..3bef091 100644
--- a/drivers/gpu/drm/i915/i915_reg.h
+++ b/drivers/gpu/drm/i915/i915_reg.h
@@ -1791,6 +1791,7 @@
#define DSPFW1 0x70034
#define DSPFW2 0x70038
+#define G4X_FBC_WM_EN (1<<31) /* GM45+ only */
#define DSPFW3 0x7003c
#define IGD_SELF_REFRESH_EN (1<<30)
diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index 7a5fb79..be1fb2b 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -1061,6 +1061,9 @@ static void g4x_enable_fbc(struct drm_crtc *crtc, unsigned long interval)
(interval << DPFC_RECOMP_TIMER_COUNT_SHIFT));
I915_WRITE(DPFC_FENCE_YOFF, crtc->y);
+ /* Use FBC watermark calculations */
+ I915_WRITE(DSPFW2, I915_READ(DSPFW2) | G4X_FBC_WM_EN);
+
/* enable it... */
I915_WRITE(DPFC_CONTROL, I915_READ(DPFC_CONTROL) | DPFC_CTL_EN);
@@ -1078,6 +1081,8 @@ void g4x_disable_fbc(struct drm_device *dev)
I915_WRITE(DPFC_CONTROL, dpfc_ctl);
intel_wait_for_vblank(dev);
+ I915_WRITE(DSPFW2, I915_READ(DSPFW2) & ~G4X_FBC_WM_EN);
+
DRM_DEBUG("disabled FBC\n");
}
next prev parent reply other threads:[~2009-10-08 17:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 22:40 2.6.32 regression (bisected): Video tearing/glitching with T400 laptops Theodore Ts'o
2009-10-02 22:44 ` Jesse Barnes
2009-10-04 13:43 ` Arkadiusz Miskiewicz
2009-10-05 20:47 ` Jesse Barnes
2009-10-08 17:36 ` Jesse Barnes [this message]
2009-10-10 20:41 ` Theodore Tso
2009-10-12 16:54 ` Jesse Barnes
2009-10-12 18:46 ` Carlos R. Mafra
2009-10-12 19:05 ` Jesse Barnes
2009-10-13 2:31 ` Theodore Tso
2009-10-13 17:01 ` Jesse Barnes
2009-10-13 19:00 ` Theodore Tso
2009-10-13 19:14 ` Jesse Barnes
2009-10-14 21:22 ` Jesse Barnes
2009-10-15 2:26 ` Theodore Tso
2009-10-15 4:02 ` Theodore Tso
2009-10-19 1:04 ` Jesse Barnes
2009-10-19 1:15 ` Jesse Barnes
2009-10-21 4:48 ` Theodore Tso
2009-10-26 7:25 ` Paul Rolland
2009-10-27 16:37 ` Johan Hovold
2009-10-15 15:30 ` Jesse Barnes
2009-10-15 1:23 ` Theodore Tso
2009-10-13 19:19 ` Fabio Comolli
2009-10-13 19:25 ` Jesse Barnes
2009-10-13 20:03 ` Fabio Comolli
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=20091008103620.5e5aae66@jbarnes-g45 \
--to=jbarnes@virtuousgeek.org \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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