All of lore.kernel.org
 help / color / mirror / Atom feed
From: ville.syrjala@linux.intel.com
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/3] drm/i915: MST link training locking and cleanups
Date: Thu, 27 Aug 2015 18:36:47 +0300	[thread overview]
Message-ID: <1440689810-29585-1-git-send-email-ville.syrjala@linux.intel.com> (raw)

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

While glancing at the MST hpd code I noticed we have no locking in there
to protect the link retraining against a concurrent modeset. So I added some,
and then ocd struct and had to clean up the code a bit.

These patches are available at 
git://github.com/vsyrjala/linux.git mst_fixes_cleanups

In the repo I've also included an earlier patch which attempts to enable
the DDI PLL for MST on SKL [1]

[1] http://lists.freedesktop.org/archives/intel-gfx/2015-August/073965.html

Ville Syrjälä (3):
  drm/i915: Protect MST retraining with connection_mutex
  drm/i915: Flatten the mst suspend/resume functions a bit
  drm/i915: Flatten intel_dp_check_mst_status()

 drivers/gpu/drm/i915/intel_dp.c | 127 ++++++++++++++++++++--------------------
 1 file changed, 65 insertions(+), 62 deletions(-)

-- 
2.4.6

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2015-08-27 15:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 15:36 ville.syrjala [this message]
2015-08-27 15:36 ` [PATCH 1/3] drm/i915: Protect MST retraining with connection_mutex ville.syrjala
2015-09-03 12:11   ` Ville Syrjälä
2015-09-16 11:48     ` Maarten Lankhorst
2015-09-23  8:01       ` Daniel Vetter
2015-08-27 15:36 ` [PATCH 2/3] drm/i915: Flatten the mst suspend/resume functions a bit ville.syrjala
2015-09-16 12:28   ` Maarten Lankhorst
2015-08-27 15:36 ` [PATCH 3/3] drm/i915: Flatten intel_dp_check_mst_status() ville.syrjala
2015-09-16 13:07   ` Maarten Lankhorst

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=1440689810-29585-1-git-send-email-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.intel.com \
    --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 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.