From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 41561] [r600 KMS] Hotplug detect does not work for HDMI monitor on Fusion E-350 board
Date: Fri, 7 Oct 2011 09:26:08 -0700 (PDT) [thread overview]
Message-ID: <20111007162608.DA08813007C@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-41561-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=41561
--- Comment #3 from Simon Farnsworth <simon.farnsworth@onelan.co.uk> 2011-10-07 09:26:08 PDT ---
So, I think I see the proximate cause of the bug, but not the reason for it:
In radeon_dvi_detect at radeon_connectors.c:962, I see:
if (!force) {
ret = connector->status;
goto out;
}
A HPD interrupt causes output_poll_execute at drm_crtc_helper.c:897 to execute
connector->status = connector->funcs->detect(connector, false); as a
result, I cannot see how a hotplug interrupt will ever result in a connector
state changing.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-10-07 16:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 15:44 [Bug 41561] New: Hotplug detect does not work for HDMI monitor on Fusion E-350 board bugzilla-daemon
2011-10-07 15:51 ` [Bug 41561] [r600 KMS] " bugzilla-daemon
2011-10-07 15:59 ` bugzilla-daemon
2011-10-07 16:07 ` bugzilla-daemon
2011-10-07 16:26 ` bugzilla-daemon [this message]
2011-10-07 17:35 ` bugzilla-daemon
2011-10-07 17:35 ` bugzilla-daemon
2011-10-07 17:53 ` bugzilla-daemon
2011-10-07 18:14 ` bugzilla-daemon
2011-10-07 18:16 ` bugzilla-daemon
2012-01-12 22:19 ` bugzilla-daemon
2012-01-21 16:46 ` bugzilla-daemon
2012-01-21 21:23 ` bugzilla-daemon
2019-11-19 8:21 ` 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=20111007162608.DA08813007C@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