From: Lyude <cpaul@redhat.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] Revert "sna: Refresh last detection timestamp on hotplug notifies"
Date: Fri, 17 Jun 2016 16:30:55 -0400 [thread overview]
Message-ID: <1466195455.7789.7.camel@redhat.com> (raw)
In-Reply-To: <20160617195712.GD15272@nuc-i3427.alporthouse.com>
On Fri, 2016-06-17 at 20:57 +0100, Chris Wilson wrote:
> On Fri, Jun 17, 2016 at 03:44:34PM -0400, Lyude wrote:
> >
> > From: Lyude Paul <cpaul@redhat.com>
> >
> > DRM does not always update the status of each connector during a
> > hotplug event, and it's generally expected that userspace is
> > supposed to
> > handle that by reprobing. This happens in a couple situations:
> > suspend/resume, MST hotplugs, and probably a few others. As a
> > result,
This was meant more to be an example of when DRM connector states
aren't consistent. This being said; i915 does do a reprobe on resuming
so that is still true. Just to make sure; you saw the IRC convo on this
airlied/danvet had right?
> > making this assumption actually breaks MST hotplugging.
> Generally expected? So logind reprobes? We force a probe on wakeup?
> -Chris
>
--
Cheers,
Lyude
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-17 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 19:44 [PATCH v2] Revert "sna: Refresh last detection timestamp on hotplug notifies" Lyude
2016-06-17 19:57 ` Chris Wilson
2016-06-17 20:30 ` Lyude [this message]
2016-06-27 20:07 ` Dave Airlie
2016-06-22 12:33 ` ✗ Ro.CI.BAT: failure for Revert "sna: Refresh last detection timestamp on hotplug notifies" (rev2) Patchwork
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=1466195455.7789.7.camel@redhat.com \
--to=cpaul@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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