From: Adam Jackson <ajax@redhat.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: mmarek@suse.cz, intel-gfx@lists.freedesktop.org
Subject: Re: Valid DP connection without EDID?
Date: Fri, 14 Sep 2012 11:25:03 -0400 [thread overview]
Message-ID: <50534C4F.6020607@redhat.com> (raw)
In-Reply-To: <s5hr4q4znyt.wl%tiwai@suse.de>
On 9/14/12 10:19 AM, Takashi Iwai wrote:
> Hi,
>
> we've got a machine showing a ghost DP2 output on a docking station.
> The docking station has only one DP port and it's connected to DP1.
> As a result, we get an DP2 active output containing the bogus VESA
> standard modes 1024x768, 800x600, 640x480 although it's not connected
> at all.
>
> Looking a bit deeply on it, it seems that the connector gives actually
> the valid DPCD. So intel_dp_detect() returns
> connector_status_connected. But since there is no real connection,
> EDID isn't obtained. Thus of course no valid modes set.
Can you be more specific here? What DPCD does it return? Does it claim
to be a branch device? We don't currently get that case right, try for
instance plugging in a DP->VGA pigtail.
> A quick patch below adds (moves) a check of EDID and returns the
> disconnected state when no valid EDID is returned. An open question
> is whether this is really safe. Is there any case where no valid EDID
> is returned but the connection is still valid?
DisplayPort requires EDID. There may be a platform method for obtaining
it for eDP, but for normal DP it has to exist over AUXCH.
DVI and HDMI require it too, in fact. The only one that doesn't is VGA.
- ajax
next prev parent reply other threads:[~2012-09-14 15:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 14:19 Valid DP connection without EDID? Takashi Iwai
2012-09-14 15:25 ` Adam Jackson [this message]
2012-09-17 8:16 ` Takashi Iwai
2012-09-17 8:21 ` Dave Airlie
2012-09-17 8:28 ` Takashi Iwai
2012-09-17 9:11 ` Dave Airlie
2012-09-17 9:32 ` Takashi Iwai
2012-09-17 16:24 ` Adam Jackson
2012-09-18 11:01 ` Takashi Iwai
2012-09-18 14:04 ` Adam Jackson
2012-09-18 14:32 ` Takashi Iwai
2012-09-18 14:48 ` Adam Jackson
2012-09-18 15:11 ` Takashi Iwai
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=50534C4F.6020607@redhat.com \
--to=ajax@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mmarek@suse.cz \
--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 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.