All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/2] drm: link status property and DP link training failure handling
Date: Fri, 16 Dec 2016 12:29:05 +0200	[thread overview]
Message-ID: <cover.1481883920.git.jani.nikula@intel.com> (raw)

The two remaining patches from [1], rebased.

BR,
Jani.


[1] http://mid.mail-archive.com/1480984058-552-1-git-send-email-manasi.d.navare@intel.com


Manasi Navare (2):
  drm: Add a new connector atomic property for link status
  drm/i915: Implement Link Rate fallback on Link training failure

 drivers/gpu/drm/drm_atomic.c                  | 16 +++++++++
 drivers/gpu/drm/drm_atomic_helper.c           | 15 ++++++++
 drivers/gpu/drm/drm_connector.c               | 52 +++++++++++++++++++++++++++
 drivers/gpu/drm/i915/intel_dp.c               | 27 ++++++++++++++
 drivers/gpu/drm/i915/intel_dp_link_training.c | 22 ++++++++++--
 drivers/gpu/drm/i915/intel_drv.h              |  3 ++
 include/drm/drm_connector.h                   | 19 ++++++++++
 include/drm/drm_mode_config.h                 |  5 +++
 include/uapi/drm/drm_mode.h                   |  4 +++
 9 files changed, 161 insertions(+), 2 deletions(-)

-- 
2.1.4

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

             reply	other threads:[~2016-12-16 10:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16 10:29 Jani Nikula [this message]
2016-12-16 10:29 ` [PATCH 1/2] drm: Add a new connector atomic property for link status Jani Nikula
2017-02-27  9:14   ` Daniel Vetter
2017-03-01 10:32   ` Daniel Vetter
2016-12-16 10:29 ` [PATCH 2/2] drm/i915: Implement Link Rate fallback on Link training failure Jani Nikula
2017-03-01 15:44   ` Daniel Vetter
2016-12-16 10:54 ` ✗ Fi.CI.BAT: failure for drm: link status property and DP link training failure handling Patchwork
2016-12-16 13:48 ` [PATCH 0/2] " Daniel Vetter
2016-12-16 14:47   ` Jani Nikula
2016-12-17  5:47     ` Pandiyan, Dhinakaran
2016-12-18 13:43       ` [Intel-gfx] " Daniel Vetter
2016-12-19 23:15         ` Pandiyan, Dhinakaran
2016-12-20  9:30           ` [Intel-gfx] " Daniel Vetter
2017-01-11 20:37             ` Manasi Navare
2017-01-18 21:05   ` Martin Peres
2017-01-19  9:18     ` Jani Nikula
2017-01-20 16:29       ` [Intel-gfx] " Martin Peres
2017-01-20 16:44         ` Jani Nikula
2017-01-20 17:23           ` Martin Peres
2017-01-19 11:34     ` [Intel-gfx] " Ville Syrjälä
2017-01-20 16:27       ` Martin Peres
2017-01-25  2:40         ` [Intel-gfx] " Manasi Navare

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=cover.1481883920.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --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.