All of 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 18:12:56 +0200	[thread overview]
Message-ID: <s5hehsbtmgn.wl%tiwai@suse.de> (raw)
In-Reply-To: <86d37vo38m.fsf@sumi.keithp.com>

At Thu, 29 Mar 2012 08:07:05 -0700,
Keith Packard wrote:
> 
> On Thu, 29 Mar 2012 13:44:28 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> 
> > In conjunction with bits Power Sequence Progress field and Power Cycle
> > Delay Active, this bit set to a one indicates that the panel is
> > currently powered up or is currently in the power down sequence and it
> > is unsafe to change the timing, port, and DPLL registers for the pipe or
> > transcoder that is assigned to the panel output.
> 
> The theory was that as we don't touch the DPLL and only modify the
> scaler, that the panel wouldn't care. I wonder what's confusing this one...

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.  Even BIOS can't recover the problem
by itself, too, as it seems.  Then, keep the machine rest for long
time and boot up, now the problem is gone.

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.


thanks,

Takashi

  reply	other threads:[~2012-03-29 16:12 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 [this message]
2012-03-29 16:57         ` Keith Packard
2012-03-29 18:02           ` Takashi Iwai
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=s5hehsbtmgn.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 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.