Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Keith Packard <keithp@keithp.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Broken LVDS output at mode changes
Date: Thu, 29 Mar 2012 20:02:01 +0200	[thread overview]
Message-ID: <s5hwr63s2ue.wl%tiwai@suse.de> (raw)
In-Reply-To: <86398rny4a.fsf@sumi.keithp.com>

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

  reply	other threads:[~2012-03-29 18:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 13:29 Broken LVDS output at mode changes Takashi Iwai
2012-03-29 12:16 ` Daniel Vetter
2012-03-29 12:44   ` Chris Wilson
2012-03-29 12:51     ` Daniel Vetter
2012-03-29 12:55       ` Takashi Iwai
2012-03-29 15:07     ` Keith Packard
2012-03-29 16:12       ` Takashi Iwai
2012-03-29 16:57         ` Keith Packard
2012-03-29 18:02           ` Takashi Iwai [this message]
2012-03-30  4:27             ` Keith Packard
2012-03-30 16:56     ` 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=s5hwr63s2ue.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    /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