linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Juston Li <juston.li@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	mario.limonciello@dell.com, linux-kernel@vger.kernel.org,
	nathan.d.ciobanu@intel.com, jared_dominguez@dell.com
Subject: Re: [Intel-gfx] [RESEND PATCH v2 0/2] Check MST topology change on resume
Date: Wed, 24 Oct 2018 10:57:50 +0200	[thread overview]
Message-ID: <20181024085750.GK324@phenom.ffwll.local> (raw)
In-Reply-To: <20181024021925.27026-1-juston.li@intel.com>

On Tue, Oct 23, 2018 at 07:19:23PM -0700, Juston Li wrote:
> 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>

For formality, does this also imply a reviewed-by tag?

For merging propably best we wait for the backmerge and the push these in
through drm-misc-next-fixes.

Well for drm-misc-next-fixes drm-misc maintainers need to roll the tree
forward. Either way needs synchronization. Plus an ack from drm-intel
maintainers.
-Daniel

> 
> 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
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  parent reply	other threads:[~2018-10-24  8:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24  2:19 [RESEND PATCH v2 0/2] Check MST topology change on resume Juston Li
2018-10-24  2:19 ` [RESEND PATCH v2 1/2] drm/dp/mst: Reprobe EDID for MST ports " 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 ` Daniel Vetter [this message]
2018-10-24 16:37   ` [Intel-gfx] [RESEND PATCH v2 0/2] Check MST topology change on resume 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=20181024085750.GK324@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jared_dominguez@dell.com \
    --cc=juston.li@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).