From: Jeff Chua <jeff.chua.linux@gmail.com>
To: Carl Worth <cworth@cworth.org>, Eric Anholt <eric@anholt.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Commit cfecde435dda78248d6fcdc424bed68d5db6be0b turns screen blank
Date: Fri, 4 Jun 2010 16:00:16 +0800 (SGT) [thread overview]
Message-ID: <Pine.LNX.4.64.1006041552280.2417@boston.corp.fedex.com> (raw)
The following commit causes screen to become blank. Upon boot up, screen
becomes blank (monitor can't sync to pc) with i915 compiled in the
kernel. With i915 as module, system boots up fine, but becomes blank as
soon as the module is loaded.
Reverting it solves the problem. Problem only happens only Dell Optiplex
780 with external LCD. But, works fine on Lenovo X201s internal LCD.
Thanks,
Jeff
commit cfecde435dda78248d6fcdc424bed68d5db6be0b
Author: Carl Worth <cworth@cworth.org>
Date: Thu Apr 8 23:31:57 2010 -0700
drm/i915: Don't enable pipe/plane/VCO early (wait for DPMS on).
The existing code handling the DPMS ON event is much more careful to
ensure that these registers are enabled according to strict sequencing
requirements. Enabling these early in mode_set simply defeats that.
Signed-off-by: Carl Worth <cworth@cworth.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index 3ee68bc..243dfb8 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -3463,11 +3463,6 @@ static int intel_crtc_mode_set(struct drm_crtc *crtc,
pipeconf &= ~PIPEACONF_DOUBLE_WIDE;
}
- dspcntr |= DISPLAY_PLANE_ENABLE;
- pipeconf |= PIPEACONF_ENABLE;
- dpll |= DPLL_VCO_ENABLE;
-
-
/* Disable the panel fitter if it was on our pipe */
if (!HAS_PCH_SPLIT(dev) && intel_panel_fitter_pipe(dev) == pipe)
I915_WRITE(PFIT_CONTROL, 0);
next reply other threads:[~2010-06-04 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 8:00 Jeff Chua [this message]
2010-06-04 15:27 ` Nick Bowler
2010-06-04 17:52 ` Jeff Chua
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=Pine.LNX.4.64.1006041552280.2417@boston.corp.fedex.com \
--to=jeff.chua.linux@gmail.com \
--cc=cworth@cworth.org \
--cc=eric@anholt.net \
--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
all inboxes | Powered by JetHome®