linux-kernel - Re: [2.6.39] drm/i915: blank screen on Lenovo Ideapad U160

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 16 Jun 2011 00:03:38 +0200
From:	Dirk Gouders <gouders@...bocholt.fh-gelsenkirchen.de>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	linux-kernel@...r.kernel.org,
	Chris Wilson <chris@...is-wilson.co.uk>
Subject: Re: [2.6.39] drm/i915: blank screen on Lenovo Ideapad U160

Jesse Barnes <jbarnes@...tuousgeek.org> writes:

> Oh is this not an LVDS panel?  I'm curious which of the port disables
> is at fault in your config then.  If you have an eDP panel, it would
> likely be the PCH_DP_D write.  It could be a side effect of the
> PANEL_UNLOCK_REGS write as well though, can you try commenting each of
> those out?

Yes, you are right.  Commenting out a single line helps:

diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index 81a9059..ed95cbf 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -1356,7 +1356,7 @@ static void intel_disable_pch_ports(struct drm_i915_private *dev_priv,
        u32 reg, val;
 
        val = I915_READ(PCH_PP_CONTROL);
-       I915_WRITE(PCH_PP_CONTROL, val | PANEL_UNLOCK_REGS);
+       //I915_WRITE(PCH_PP_CONTROL, val | PANEL_UNLOCK_REGS);
 
        disable_pch_dp(dev_priv, pipe, PCH_DP_B);
        disable_pch_dp(dev_priv, pipe, PCH_DP_C);

Dirk
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/