From mboxrd@z Thu Jan  1 00:00:00 1970
From: Takashi Iwai <tiwai@suse.de>
Subject: Re: Broken LVDS output at mode changes
Date: Thu, 29 Mar 2012 20:02:01 +0200
Message-ID: <s5hwr63s2ue.wl%tiwai@suse.de>
References: <s5h4nt8zwf3.wl%tiwai@suse.de>
	<20120329121638.GA20275@phenom.ffwll.local>
	<1333025081_141778@CP5-2952> <86d37vo38m.fsf@sumi.keithp.com>
	<s5hehsbtmgn.wl%tiwai@suse.de> <86398rny4a.fsf@sumi.keithp.com>
Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15])
	by gabe.freedesktop.org (Postfix) with ESMTP id 5DCFC9E78C
	for <intel-gfx@lists.freedesktop.org>;
	Thu, 29 Mar 2012 11:02:03 -0700 (PDT)
In-Reply-To: <86398rny4a.fsf@sumi.keithp.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
To: Keith Packard <keithp@keithp.com>
Cc: intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

At Thu, 29 Mar 2012 09:57:41 -0700,
Keith Packard wrote:
> 
> <#part sign=pgpmime>
> On Thu, 29 Mar 2012 18:12:56 +0200, Takashi Iwai <tiwai@suse.de> wrote:
> 
> > The strange thing is that, although you can recover the display by
> > turning off LVDS and on again once when the problem happens, but then
> > the display starts flickering.  And, the flickering continues even
> > after reboot on BIOS boot screen.
> 
> Yeah, it's clearly the panel which is confused. It would be nice to know
> what happened to the LVDS signal which caused this problem with the
> panel.

I'll try to poke someone in HP.

> > BTW, now I tested to disable LVDS unconditionally on different
> > platforms as Daniel suggested.  All worked fine, and I saw no
> > regressions.  Tested on IVY, SNB, ILK, GM45 and PineView.
> 
> That's not surprising -- pre-PCH platforms disabled the LVDS
> anyways.
> 
> I wonder if we could fix this by being more careful about the order of
> register operations during LVDS mode setting...

Sure, that'd be a preferred option.
If you have any easy test in mind, let me know.


thanks,

Takashi