From: Jani Nikula <jani.nikula@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, "Peres,
Martin" <martin.peres@intel.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] drm: link status property and DP link training failure handling
Date: Fri, 16 Dec 2016 16:47:06 +0200 [thread overview]
Message-ID: <87eg18nd79.fsf@intel.com> (raw)
In-Reply-To: <20161216134825.vbiyyilvud7bpeem@phenom.ffwll.local>
On Fri, 16 Dec 2016, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Fri, Dec 16, 2016 at 12:29:05PM +0200, Jani Nikula wrote:
>> 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
>
> Just for the record, I think the only thing missing here is the Xorg
> review on the -modesetting patch. As soon as we have that I can vacuum
> this up (probably best through drm-misc, but not sure).
Yeah I rebased this (and provided a debug hack privately) so Martin can
test the modesetting changes.
BR,
Jani.
> -Daniel
>
>>
>>
>> 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
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-12-16 14:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 10:29 [PATCH 0/2] drm: link status property and DP link training failure handling Jani Nikula
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 13:48 ` [PATCH 0/2] drm: link status property and DP link training failure handling Daniel Vetter
2016-12-16 14:47 ` Jani Nikula [this message]
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=87eg18nd79.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=martin.peres@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).