dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 33011] HDMI-A-1 Does not work after resume (But claims it does)
Date: Fri,  4 Feb 2011 09:13:45 -0800 (PST)	[thread overview]
Message-ID: <20110204171345.31ADE13004D@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-33011-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=33011

--- Comment #17 from Alex Deucher <agd5f@yahoo.com> 2011-02-04 09:13:44 PST ---
(In reply to comment #16)
> Just a few followups. It doesn't seem to be related to the docking station
> switching. The problem occurs even without the docking port.
> 
> Additionally, if I plug an HDMI cable into the laptop while the docking station
> is plugged in, the monitor is not detected at all. Where-as after I resume and
> have a problem, the monitor is detected, it just doesn't get sync. So the
> docking station switching disables the port "more" than the resume problem.

This is consistent with the gpio controlled data and ddc routing that I suspect
is happening.  There's probably a small mux which routes the ddc/hdp lines (for
detection and edid) and the data lines (for the actual video signal) between
the HDMI port on the laptop and the DVI port on the docking station.  When you
dock, the acpi docking method probably calls some other method which switches
the mux to the other connector.  The same thing probably happens on undock. 
The question is, is this handled by an acpi method or some platform specific
gpio/i2c setup.  Newer radeon-based laptops that use a mux like this have a
special entry in the vbios object table that describes the mux.  Unfortunately,
your system doesn't have this, so it's probably some system-specific
configuration.  When you suspend, the mux loses power and goes into some
undefined state on resume the signals are not routed correctly since the mux
state is wrong.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-02-04 17:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12  6:23 [Bug 33011] New: HDMI-A-1 Does not work if disconnected at power-up (But claims it does) bugzilla-daemon
2011-01-12  6:38 ` [Bug 33011] " bugzilla-daemon
2011-01-14  6:01 ` [Bug 33011] HDMI-A-1 Does not work after resume " bugzilla-daemon
2011-01-14  6:03 ` bugzilla-daemon
2011-01-14  6:04 ` bugzilla-daemon
2011-01-21  0:19 ` bugzilla-daemon
2011-01-21  0:22 ` bugzilla-daemon
2011-01-22  6:55 ` bugzilla-daemon
2011-01-24  6:03 ` bugzilla-daemon
2011-01-26  4:47 ` bugzilla-daemon
2011-01-26  4:47 ` bugzilla-daemon
2011-01-26  4:49 ` bugzilla-daemon
2011-01-26  6:22 ` bugzilla-daemon
2011-01-26 17:40 ` bugzilla-daemon
2011-01-26 18:36 ` bugzilla-daemon
2011-01-27  6:36 ` bugzilla-daemon
2011-01-27  6:36 ` bugzilla-daemon
2011-01-28  7:04 ` bugzilla-daemon
2011-02-04  8:03 ` bugzilla-daemon
2011-02-04 17:13 ` bugzilla-daemon [this message]
2011-02-09 22:12 ` bugzilla-daemon
2011-02-09 22:14 ` bugzilla-daemon
2011-03-07 20:17 ` [Bug 33011] [RADEON:KMS:RV530M:MUX] " bugzilla-daemon
2016-02-26  6:05 ` bugzilla-daemon

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=20110204171345.31ADE13004D@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@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;
as well as URLs for NNTP newsgroup(s).