From: Keith Packard <keithp@keithp.com>
To: Dave Airlie <airlied@redhat.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org,
Keith Packard <keithp@keithp.com>
Subject: drm/i915: Disabling unused outputs on CPT is broken
Date: Sat, 6 Aug 2011 10:54:04 -0700 [thread overview]
Message-ID: <1312653248-3487-1-git-send-email-keithp@keithp.com> (raw)
Here's a fun sequence:
$ xrandr --output LVDS1 --auto --crtc 1
$ sudo chvt 1
(then switch back to X)
The LVDS goes black. Why? The LVDS is *disabled*. Turns out that the
cause was that after the mode was all nicely set,
intel_disable_pch_ports went and turned it back off.
Well, a couple of weeks ago, we found that intel_disable_pch_ports was
doing the same thing to DP ports, and the cause was that the way to
tell which port a DP output was running from is different on CPT that
on every other chip. We fixed that, but didn't (foolishly) review the
non-DP code.
Oddly, the non-DP code had essentially the same bug:
[PATCH 3/4] drm/i915: Fix PCH port pipe select in CPT disable paths
Also in this sequence is some code that validates the LVDS panel power
sequencing which discovered that the LVDS panel wasn't being disabled
correctly because the LVDS registers were locked in the DPMS
function. Instead of trying to get the LVDS locking right, I've just
unlocked the registers in the lvds initialization code and left them
unlocked after that:
[PATCH 1/4] drm/i915: Wait for LVDS panel power sequence
[PATCH 2/4] drm/i915: Leave LVDS registers unlocked
Finally, I removed an unused argument to dp_pipe_enable while I was
poking around in that code:
[PATCH 4/4] drm/i915: Remove unused 'reg' argument to dp_pipe_enable
--
keith.packard@intel.com
next reply other threads:[~2011-08-06 17:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 17:54 Keith Packard [this message]
2011-08-06 17:54 ` [PATCH 1/4] drm/i915: Wait for LVDS panel power sequence Keith Packard
2011-08-08 16:27 ` [Intel-gfx] " Jesse Barnes
2011-08-08 18:40 ` Keith Packard
2011-08-08 18:50 ` Jesse Barnes
2011-08-06 17:54 ` [PATCH 2/4] drm/i915: Leave LVDS registers unlocked Keith Packard
2011-08-08 16:30 ` [Intel-gfx] " Jesse Barnes
2011-08-08 16:30 ` Jesse Barnes
2011-08-08 18:25 ` [Intel-gfx] " Keith Packard
2011-08-08 18:25 ` Keith Packard
2011-08-08 18:42 ` Keith Packard
2011-08-08 18:42 ` Keith Packard
2011-08-08 18:49 ` [Intel-gfx] " Jesse Barnes
2011-08-08 19:53 ` Keith Packard
2011-08-08 19:53 ` Keith Packard
2011-08-08 20:01 ` Jesse Barnes
2011-08-08 20:24 ` Keith Packard
2011-08-08 20:25 ` Jesse Barnes
2011-08-06 17:54 ` [PATCH 3/4] drm/i915: Fix PCH port pipe select in CPT disable paths Keith Packard
2011-08-08 16:31 ` [Intel-gfx] " Jesse Barnes
2011-08-06 17:54 ` [PATCH 4/4] drm/i915: Remove unused 'reg' argument to dp_pipe_enabled Keith Packard
2011-08-08 16:32 ` [Intel-gfx] " 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=1312653248-3487-1-git-send-email-keithp@keithp.com \
--to=keithp@keithp.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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.