From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org,
"Kirill A . Shutemov" <kirill@shutemov.name>,
drm-intel-fixes@lists.freedesktop.org,
Rui Tiago Matos <tiagomatos@gmail.com>
Subject: Re: [PATCH] drm/i915: Refresh that status of MST capable connectors in ->detect()
Date: Fri, 21 Oct 2016 18:56:36 +0300 [thread overview]
Message-ID: <20161021155636.GT4329@intel.com> (raw)
In-Reply-To: <20161021154638.GS25629@nuc-i3427.alporthouse.com>
On Fri, Oct 21, 2016 at 04:46:38PM +0100, Chris Wilson wrote:
> On Fri, Oct 21, 2016 at 04:44:38PM +0300, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Once we've determined that the sink is MST capable we never end up
> > running through the full detect cycle again, despite getting HPDs.
> > Fix tht by ripping out the incorrect piece of code responsible.
>
> Ah, the missing magic is the call to intel_dp_configure_mst() right?
Yeah, if the cable is still physically connected we do that. And if not
we'll take the earlier way out to inform the topology manager that
we're no longer doing MST.
>
> With that understood,
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-10-21 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 13:44 [PATCH] drm/i915: Refresh that status of MST capable connectors in ->detect() ville.syrjala
2016-10-21 14:17 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-10-26 8:15 ` Ville Syrjälä
2016-10-21 15:46 ` [PATCH] " Chris Wilson
2016-10-21 15:56 ` Ville Syrjälä [this message]
2016-10-26 8:57 ` Ville Syrjälä
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=20161021155636.GT4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=drm-intel-fixes@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kirill@shutemov.name \
--cc=tiagomatos@gmail.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 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.