From: Juston Li <juston.li@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: lyude@redhat.com, clinton.a.taylor@intel.com,
nathan.d.ciobanu@intel.com, mario.limonciello@dell.com,
jared_dominguez@dell.com, linux-kernel@vger.kernel.org,
Juston Li <juston.li@intel.com>
Subject: [RESEND PATCH v2 0/2] Check MST topology change on resume
Date: Tue, 23 Oct 2018 19:19:23 -0700 [thread overview]
Message-ID: <20181024021925.27026-1-juston.li@intel.com> (raw)
Updated and resending these patches from Lyude:
https://lkml.org/lkml/2016/5/19/361
https://lkml.org/lkml/2016/5/19/360
As Lyude explains in patch 1/2, we can't rely on MST hubs to handle
hotplugs during suspend. This patchset will check if any EDID's changed
upon resume and reset the MST connections if they did.
This resolves issues with monitors not being detected when hotplugging them
during suspend.
Signed-off-by: Juston Li <juston.li@intel.com>
Changes since v1:
- update functions that have been renamed since the original patch
- add a null check for the cached EDID in case a new device was added
- checkpatch fixes
Lyude (2):
drm/dp/mst: Reprobe EDID for MST ports on resume
drm/i915/mst: Reset MST after resume when necessary
drivers/gpu/drm/drm_dp_mst_topology.c | 94 ++++++++++++++++++++++++++-
drivers/gpu/drm/i915/intel_dp.c | 7 +-
2 files changed, 99 insertions(+), 2 deletions(-)
--
2.17.2
next reply other threads:[~2018-10-24 3:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 2:19 Juston Li [this message]
2018-10-24 2:19 ` [RESEND PATCH v2 1/2] drm/dp/mst: Reprobe EDID for MST ports on resume Juston Li
2018-10-24 22:09 ` Lyude Paul
2018-10-24 22:45 ` Li, Juston
2018-11-09 0:43 ` Lyude Paul
2018-11-26 21:53 ` Li, Juston
2018-11-26 22:35 ` Lyude Paul
2018-10-24 23:02 ` Lyude Paul
2018-10-24 2:19 ` [RESEND PATCH v2 2/2] drm/i915/mst: Reset MST after resume when necessary Juston Li
2018-10-24 8:57 ` [Intel-gfx] [RESEND PATCH v2 0/2] Check MST topology change on resume Daniel Vetter
2018-10-24 16:37 ` Li, Juston
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=20181024021925.27026-1-juston.li@intel.com \
--to=juston.li@intel.com \
--cc=clinton.a.taylor@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jared_dominguez@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=mario.limonciello@dell.com \
--cc=nathan.d.ciobanu@intel.com \
/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).