Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 17 Sep 2012 12:24:36 -0400	[thread overview]
Message-ID: <1347899076.25266.46.camel@atropine> (raw)
In-Reply-To: <s5hsjahxae5.wl%tiwai@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 1905 bytes --]

On Mon, 2012-09-17 at 11:32 +0200, Takashi Iwai wrote:
> At Mon, 17 Sep 2012 19:11:34 +1000,
> Dave Airlie wrote:
> > On Mon, Sep 17, 2012 at 6:28 PM, Takashi Iwai <tiwai@suse.de> wrote:
> > > At Mon, 17 Sep 2012 18:21:47 +1000,
> > > Dave Airlie wrote:
> > >> On Mon, Sep 17, 2012 at 6:16 PM, Takashi Iwai <tiwai@suse.de> wrote:
> > >> > At Fri, 14 Sep 2012 11:25:03 -0400,
> > >> > Adam Jackson wrote:
> > >> >>
> > >> >> Can you be more specific here?  What DPCD does it return?
> > >> >
> > >> > It shows "DPCD: 110a820100030181"

So dpcd[0x5] is 0x03, and drm_dp_helper.h says:

#define DP_DOWNSTREAMPORT_PRESENT           0x005
# define DP_DWN_STRM_PORT_PRESENT           (1 << 0)
# define DP_DWN_STRM_PORT_TYPE_MASK         0x06
/* 00b = DisplayPort */
/* 01b = Analog */
/* 10b = TMDS or HDMI */
/* 11b = Other */
# define DP_FORMAT_CONVERSION               (1 << 3)

So there we go, it's a branch device with VGA downstream of it.  We need
to figure out the connectivity of the downstream port.

> > > Checking DPCD bits might work, but I have no exact spec of DPCD, so no
> > > idea whether the above is really wrong or not.
> > 
> > Is there a VGA port on the docking station, it might have a DP->VGA in
> > it, or dual-link DVI port.
> 
> Ah, right, that's the missing piece!
> 
> It's a DP->VGA conversion indeed.  Plugging to a VGA connector appears
> as DP2.  Oh well, I didn't think of this possibility at all.
> 
> But then this makes me wonder how to solve the problem at best.
> It's obviously a bogus connection status returned from the driver.
> DP2 advertises itself as if connected.

I wouldn't quite say it's bogus, more that we're describing the
connection status of "the nearest DP device" as if it were the
connection status of the whole wire.

I started a patch series for this a bit ago, I'll send it on
momentarily.

- ajax

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2012-09-17 16:24 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
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 [this message]
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=1347899076.25266.46.camel@atropine \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox