From: Lyude Paul <lyude@redhat.com>
To: stable@vger.kernel.org
Cc: Justin Forbes <jforbes@redhat.com>, Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH] drm/i915: Refresh that status of MST capable connectors in ->detect()
Date: Thu, 10 Nov 2016 17:18:51 -0500 [thread overview]
Message-ID: <1478816331.21919.1.camel@redhat.com> (raw)
In-Reply-To: <1478812707-26985-1-git-send-email-lyude@redhat.com>
whoops, didn't realize this wasn't in linus's branch. Feel free to
ignore for now greg
On Thu, 2016-11-10 at 16:18 -0500, Lyude wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Commit 1aab956c7b8872fb6976328316bfad62c6e67cf8 upstream.
>
> 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.
>
> This got broken when I moved the long HPD handling to the ->detect()
> hook, but failed to remove the leftover code.
>
> Cc: Ander Conselvan de Oliveira <conselvan2@gmail.com>
> Cc: drm-intel-fixes@lists.freedesktop.org
> Cc: Rui Tiago Matos <tiagomatos@gmail.com>
> Tested-by: Rui Tiago Matos <tiagomatos@gmail.com>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=98323
> Cc: Kirill A. Shutemov <kirill@shutemov.name>
> Tested-by: Kirill A. Shutemov <kirill@shutemov.name>
> References: https://bugs.freedesktop.org/show_bug.cgi?id=98306
> Fixes: 27d4efc5591a ("drm/i915: Move long hpd handling into the
> hotplug work")
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Link: http://patchwork.freedesktop.org/patch/msgid/1477057478-29328-1
> -git-send-email-ville.syrjala@linux.intel.com
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/intel_dp.c | 10 ----------
> 1 file changed, 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c
> b/drivers/gpu/drm/i915/intel_dp.c
> index 3051182..b8aeb28 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -4323,21 +4323,11 @@ static enum drm_connector_status
> intel_dp_detect(struct drm_connector *connector, bool force)
> {
> struct intel_dp *intel_dp = intel_attached_dp(connector);
> - struct intel_digital_port *intel_dig_port =
> dp_to_dig_port(intel_dp);
> - struct intel_encoder *intel_encoder = &intel_dig_port->base;
> enum drm_connector_status status = connector->status;
>
> DRM_DEBUG_KMS("[CONNECTOR:%d:%s]\n",
> connector->base.id, connector->name);
>
> - if (intel_dp->is_mst) {
> - /* MST devices are disconnected from a monitor POV
> */
> - intel_dp_unset_edid(intel_dp);
> - if (intel_encoder->type != INTEL_OUTPUT_EDP)
> - intel_encoder->type = INTEL_OUTPUT_DP;
> - return connector_status_disconnected;
> - }
> -
> /* If full detect is not performed yet, do a full detect */
> if (!intel_dp->detect_done)
> status = intel_dp_long_pulse(intel_dp-
> >attached_connector);
prev parent reply other threads:[~2016-11-10 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFbkSA0mG4ex69ng-dXYrCCvF8a9gnjmCz53Fo5kA2+AUWP9Uw@mail.gmail.com>
2016-11-10 21:18 ` [PATCH] drm/i915: Refresh that status of MST capable connectors in ->detect() Lyude
2016-11-10 22:18 ` Lyude Paul [this message]
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=1478816331.21919.1.camel@redhat.com \
--to=lyude@redhat.com \
--cc=hdegoede@redhat.com \
--cc=jforbes@redhat.com \
--cc=stable@vger.kernel.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).