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 106529] dc=1 kernels somehow trigger a disconnect of an lg ultrawide monitor during DP link training while attempting a wakeup
Date: Wed, 15 Aug 2018 14:43:52 +0000	[thread overview]
Message-ID: <bug-106529-502-P8k5Be77z3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106529-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1407 bytes --]

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

--- Comment #2 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Mariusz Mazur from comment #1)
> Pre-DC codepaths did not have an issue like this at all until Michel Dänzer
> created this patch: https://patchwork.freedesktop.org/patch/209464/ for bug
> 105308 thereby introducing a problem with the same effects (DC monitor gets
> disconnected on wakeup, which on multi-display causes issues) via a quite
> different approach (a deliberate DRM_MODE_DPMS_OFF & ON). But that should be
> a separate bug, I think.

FWIW, that change should have no direct effect on whether the display is
considered connected or disconnected. The only change is that when the driver
is notified that a DP display is "disconnected" (which can also happen without
a physical disconnection, e.g. if the display is turned off), it doesn't
immediately turn off the GPU's DP source anymore, but waits until either
userspace asks to turn it off, or it gets notified that a display is
"connected" again. Both "disconnect" / "connect" hotplug events are sent to
userspace before and after this change. I suspect that immediately turning off
the DP source simply happened to delay sending the "disconnect" hotplug event
to userspace enough to avoid the issue on your system.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2531 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-08-15 14:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 15:00 [Bug 106529] Kernels 4.16+ confuses KDE wrt what the primary display is when waking up multiple displays bugzilla-daemon
2018-05-15 15:01 ` [Bug 106529] Kernels 4.16+ confuse " bugzilla-daemon
2018-05-15 15:19 ` bugzilla-daemon
2018-08-09 20:07 ` [Bug 106529] dc=1 kernels somehow trigger a disconnect of an lg ultrawide monitor during DP link training while attempting a wakeup bugzilla-daemon
2018-08-09 20:29 ` bugzilla-daemon
2018-08-15 14:43 ` bugzilla-daemon [this message]
2018-08-15 16:08 ` bugzilla-daemon
2018-08-15 17:29 ` bugzilla-daemon
2018-08-16  7:36 ` bugzilla-daemon
2019-11-19  8:38 ` 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-106529-502-P8k5Be77z3@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;
as well as URLs for NNTP newsgroup(s).