From: Keith Packard <keithp@keithp.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Broken LVDS output at mode changes
Date: Thu, 29 Mar 2012 21:27:13 -0700 [thread overview]
Message-ID: <86y5qiyaqm.fsf@sumi.keithp.com> (raw)
In-Reply-To: <s5hwr63s2ue.wl%tiwai@suse.de>
<#part sign=pgpmime>
On Thu, 29 Mar 2012 20:02:01 +0200, Takashi Iwai <tiwai@suse.de> wrote:
> Sure, that'd be a preferred option.
> If you have any easy test in mind, let me know.
The way I'd love to see it tested would be to capture signal traces on
the LVDS link across mode set and see what glitches appear. That sounds
hard to do without an LVDS signal analyser...
--
keith.packard@intel.com
next prev parent reply other threads:[~2012-03-30 4:27 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
2012-03-30 4:27 ` Keith Packard [this message]
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=86y5qiyaqm.fsf@sumi.keithp.com \
--to=keithp@keithp.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tiwai@suse.de \
/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