From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 46711] Monitor not turning on after DisplayPort re-plug in Xorg
Date: Sun, 11 Jan 2015 02:29:02 +0000 [thread overview]
Message-ID: <bug-46711-502-ijDrxlOLcJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-46711-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2171 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=46711
--- Comment #21 from Branen Salmon <bugs@nenarb.net> ---
After some digging, the only differences I've been able to find between the
re-plug behavior under X (where the encoder sends no signal although the driver
thinks DPMS is ON), and the re-plug behavior under an fbdev (where the signal
returns after re-plug, as expected) are the following:
1. When the monitor is re-plugged and radeon_connector_hotplug is called,
connector->dpms is OFF in the fbdev case, but it's ON in the X case. This
means that radeon_connector_hotplug returns immediately when the monitor is
re-plugged under fbdev, and that the code in radeon_connector_hotplug is not
what's turning the encoder back on.
2. In the fbdev case, there are redundant calls to radeon_atom_encoder_dpms.
When unplugging, it's called six times with on=false, and when re-plugging,
it's called thrice, with on=false, on=true, and on=true. In the X case, it's
called only once per unplug/re-plug, with on=false and on=true, respectively.
3. In the fbdev case, drm_crtc_helper_set_config is called on re-plug, and it
calls some other functions, including radeon_encoder_set_active_device and
drm_crtc_helper_set_mode. (I realize that this may be a red herring, but
figure I should include it so that expert eyes may judge.)
drm_crtc_helper_set_config isn't called at all in the X case.
4. Forcing DPMS off with xset results in one call to
radeon_atom_encoder_dpms. Forcing DPMS on with xset results in one call to
radeon_atom_encoder_dpms and one (I think?) call to drm_crtc_helper_set_config.
(I'm not counting calls to encoders and connectors not connected to my monitor,
even though fbdev likes to traverse them all anytime something changes.)
It seems that drm_crtc_helper_set_config is doing something with the encoder
that radeon_connector_hotplug is not doing. This is my first time digging into
video code, so I have no idea what that might be. I'm going to take a break
from working on this for now, but will come back to it if no one else beats me
to it. :)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2951 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-01-11 2:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 10:22 [Bug 46711] New: Monitor not turning on after DisplayPort re-plug in Xorg bugzilla-daemon
2012-02-28 11:58 ` [Bug 46711] " bugzilla-daemon
2012-02-28 12:10 ` bugzilla-daemon
2012-02-28 15:59 ` bugzilla-daemon
2012-04-13 21:48 ` bugzilla-daemon
2012-04-13 22:28 ` bugzilla-daemon
2012-04-16 15:00 ` bugzilla-daemon
2012-04-16 15:25 ` bugzilla-daemon
2012-04-16 15:54 ` bugzilla-daemon
2012-04-16 16:07 ` bugzilla-daemon
2012-04-17 15:23 ` bugzilla-daemon
2012-04-17 15:45 ` bugzilla-daemon
2012-04-17 16:09 ` bugzilla-daemon
2012-04-17 16:37 ` bugzilla-daemon
2012-04-18 7:59 ` bugzilla-daemon
2012-04-18 8:16 ` bugzilla-daemon
2012-04-18 14:07 ` bugzilla-daemon
2012-04-20 10:07 ` bugzilla-daemon
2014-04-09 18:05 ` bugzilla-daemon
2014-04-09 22:05 ` bugzilla-daemon
2015-01-07 1:40 ` bugzilla-daemon
2015-01-11 2:29 ` bugzilla-daemon [this message]
2015-07-20 21:41 ` bugzilla-daemon
2016-03-24 10:41 ` bugzilla-daemon
2019-02-09 9:35 ` bugzilla-daemon
2019-04-19 8:14 ` bugzilla-daemon
2019-11-19 8:25 ` 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=bug-46711-502-ijDrxlOLcJ@http.bugs.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