From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/crt: Do not rely upon the HPD presence pin
Date: Sun, 10 Jun 2012 20:17:38 +0100 [thread overview]
Message-ID: <1339355858_3733@CP5-2952> (raw)
In-Reply-To: <20120610170410.GD4703@phenom.ffwll.local>
On Sun, 10 Jun 2012 19:04:10 +0200, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Fri, Jun 08, 2012 at 11:23:10PM +0100, Chris Wilson wrote:
> > On Sat, 9 Jun 2012 00:22:12 +0200, Daniel Vetter <daniel@ffwll.ch> wrote:
> > > On Thu, May 31, 2012 at 01:08:53PM +0100, Chris Wilson wrote:
> > > > Whilst most monitors do wire up the HPD presence pin, it seems quite a
> > > > few KVM do not. Therefore if we simply rely on the HPD pin being
> > > > asserted to indicate a connected monitor we fail miserable, so fall back
> > > > to performing a DCC query for the EDID.
> > > >
> > > > Reported-and-tested-by: Matthieu LAVIE <boiteamadmax@hotmail.com>
> > > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=50501
> > > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > >
> > > Ok, this blew up ... Can you please resend, with Dave's suggestion for a
> > > rectified commit message & comment and with a check added such that we
> > > don't try to do load_detect on HAS_HOTPLUG machines - I guess it doesn't
> > > work too well.
> >
> > I disagree, if we cannot trust the hw autodetection, then we know that
> > there are monitors/kvm that do not report an EDID and so we need to do
> > the whole shebang. Which will continue to annoy Linus since his machine
> > is behaving as expected given the circumstances.
>
> Well, I don't disagree on doing the whole shebang. The proplem is that the
> load-detect code as-is is gen3 only (and maybe gen4, haven't checked
> that) - it surely can't work on pch split platforms if half the registers
> we use in there are gone.
>
> Until that is fixed and properly tested on all relevant platforms, we
> should be able to help the bug reporters by simply using the edid
> detection, but bailing on the load detect stuff for all HAS_HOTPLUG
> platforms (as we do now already). I'll whip up a patch.
>
> For actual load-detect stuff is imo -next material, and I think we should
> dodge that bullet until we have an actual bug reporter wanting it ...
I can send them one of my monitors that fails to report an EDID to them
so that they can put it behind their KVM that breaks autodetection...
Coming up with a solution to handling unknown connection status is indeed
-next material, so I'm not too concerned if we punt the entire thing so
that we can do a thorough job. If we could handle unknown cleanly, it
would have prevented a lot of misery over the years with spurious TV
detection and the like.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-06-10 19:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 12:08 [PATCH] drm/i915/crt: Do not rely upon the HPD presence pin Chris Wilson
2012-05-31 12:50 ` Daniel Vetter
2012-05-31 13:34 ` Dave Airlie
2012-06-08 22:22 ` Daniel Vetter
2012-06-08 22:23 ` Chris Wilson
2012-06-10 17:04 ` Daniel Vetter
2012-06-10 19:17 ` Chris Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-11 7:29 Daniel Vetter
2012-06-11 7:58 ` Chris Wilson
2012-06-11 8:40 ` Daniel Vetter
2012-06-11 9:46 ` Chris Wilson
2012-06-11 14:38 ` Daniel Vetter
2012-06-11 14:42 ` Chris Wilson
2012-06-11 19:00 ` Daniel Vetter
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=1339355858_3733@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/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