From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107731] radeon (amdgpu) DisplayPort loss of max-resolution on DP monitor (after monitor power saving / idle)
Date: Tue, 19 Mar 2019 10:52:14 +0000 [thread overview]
Message-ID: <bug-107731-502-xc1UPrZ8OW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107731-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 961 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107731
--- Comment #7 from L.S.S. <ragnaros39216@yandex.com> ---
Unfortunately I cannot test this on my monitor (Lenovo ThinkVision P27). While
it only has options for DP or HDMI input (no Auto select), it seems to actively
cycle through the input signals when powering on, resuming from idle, or when
there's no signal on either input.
The monitor in question doesn't appear to maintain the inactive link (as well
as USB connection) when powering off, going idle, or switching input, from what
I could find out. Before using a KVM (that I'm swapping between its HDMI and DP
inputs that were connected to different places), whenever I switch the active
signal, the built-in USB hub power-cycles (devices disconnect then reconnect),
and the monitor becomes disconnected to the system connected to the now
inactive signal.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1845 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-19 10:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 1:37 [Bug 107731] radeon (amdgpu) DisplayPort loss of max-resolution on DP monitor (after monitor power saving / idle) bugzilla-daemon
2018-08-29 1:38 ` bugzilla-daemon
2019-03-10 7:44 ` bugzilla-daemon
2019-03-10 7:48 ` bugzilla-daemon
2019-03-10 7:56 ` bugzilla-daemon
2019-03-11 16:07 ` bugzilla-daemon
2019-03-17 8:08 ` bugzilla-daemon
2019-03-18 20:08 ` bugzilla-daemon
2019-03-19 10:52 ` bugzilla-daemon [this message]
2019-03-19 13:50 ` bugzilla-daemon
2019-03-19 18:27 ` bugzilla-daemon
2019-03-19 19:18 ` bugzilla-daemon
2019-03-22 17:28 ` bugzilla-daemon
2019-05-22 0:58 ` bugzilla-daemon
2019-05-22 2:20 ` bugzilla-daemon
2019-10-03 16:40 ` bugzilla-daemon
2019-11-19 8:50 ` 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-107731-502-xc1UPrZ8OW@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.