From: Manasi Navare <manasi.d.navare@intel.com>
To: Harry Wentland <harry.wentland@amd.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/5] Handle Link Training Failure during modeset
Date: Mon, 14 Nov 2016 17:14:27 -0800 [thread overview]
Message-ID: <20161115011427.GA26511@intel.com> (raw)
In-Reply-To: <29fbad5a-afda-dc8d-d38a-55fbc6d72807@amd.com>
On Mon, Nov 14, 2016 at 08:07:39PM -0500, Harry Wentland wrote:
> Overall this patch set makes sense but I think it would be good to
> move some stuff to common code instead of leaving it in i915. I'm
> thinking about patch 2 (setting the link status property) in
> particular but also tend to agree with Ville and Daniel about their
> comments for patch 5.
>
> That said, should another driver need it it shouldn't be hard to
> pull that out.
>
> Patch 1: Reviewed-by: Harry Wentland <harry.wentland@amd.com>
>
> Patch 2-5: Acked-by: Harry Wentland <harry.wentland@amd.com>
>
> Harry
>
>
Thanks for the review.
I am already moving Patch 2 set_link_status to the drm core as
per Daniel and Ville's suggestion. I will make those changes
and submit the new patches by EOD today.
Regards
Manasi
> On 2016-11-09 11:42 PM, Manasi Navare wrote:
> >Link training failure is handled by lowering the link rate first
> >until it reaches the minimum and keeping the lane count maximum
> >and then lowering the lane count until it reaches minimim. These
> >fallback values are saved and hotplug uevent is sent to the userspace
> >after setting the connector link status property to BAD. Userspace
> >should triiger another modeset on a uevent and if link status property
> >is BAD. This will retrain the link at fallback values.
> >This is repeated until the link is successfully trained.
> >
> >This has been validated to pass DP compliance.
> >
> >Manasi Navare (5):
> > drm: Add a new connector property for link status
> > drm/i915: Set link status property for DP connector
> > drm/i915: Update CRTC state if connector link status property changed
> > drm/i915: Find fallback link rate/lane count
> > drm/i915: Implement Link Rate fallback on Link training failure
> >
> > drivers/gpu/drm/drm_atomic_helper.c | 7 ++
> > drivers/gpu/drm/drm_connector.c | 17 ++++
> > drivers/gpu/drm/i915/intel_ddi.c | 21 +++-
> > drivers/gpu/drm/i915/intel_dp.c | 138 +++++++++++++++++++++++++-
> > drivers/gpu/drm/i915/intel_dp_link_training.c | 12 ++-
> > drivers/gpu/drm/i915/intel_drv.h | 12 ++-
> > include/drm/drm_connector.h | 7 +-
> > include/drm/drm_crtc.h | 5 +
> > include/uapi/drm/drm_mode.h | 4 +
> > 9 files changed, 214 insertions(+), 9 deletions(-)
> >
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-11-15 1:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 4:42 [PATCH 0/5] Handle Link Training Failure during modeset Manasi Navare
2016-11-10 4:42 ` [PATCH 1/5] drm: Add a new connector property for link status Manasi Navare
2016-11-10 4:42 ` [PATCH 2/5] drm/i915: Set link status property for DP connector Manasi Navare
2016-11-10 4:42 ` [PATCH 3/5] drm/i915: Update CRTC state if connector link status property changed Manasi Navare
2016-11-10 4:42 ` [PATCH 4/5] drm/i915: Find fallback link rate/lane count Manasi Navare
2016-11-10 4:42 ` [PATCH 5/5] drm/i915: Implement Link Rate fallback on Link training failure Manasi Navare
2016-11-10 20:58 ` [Intel-gfx] " Daniel Vetter
2016-11-11 9:41 ` Jani Nikula
2016-11-11 15:56 ` [Intel-gfx] " Manasi Navare
2016-11-11 14:08 ` Ville Syrjälä
2016-11-11 15:43 ` Manasi Navare
2016-11-10 18:19 ` [PATCH 0/5] Handle Link Training Failure during modeset Jani Nikula
2016-11-10 18:42 ` [Intel-gfx] " Deucher, Alexander
2016-11-10 18:51 ` Cheng, Tony
2016-11-11 14:05 ` Ville Syrjälä
2016-11-11 16:21 ` Cheng, Tony
2016-11-11 16:43 ` Ville Syrjälä
2016-11-11 19:42 ` Cheng, Tony
2016-11-14 7:43 ` Manasi Navare
2016-11-14 8:04 ` Daniel Vetter
2016-11-14 14:45 ` Cheng, Tony
2016-11-14 17:51 ` [Intel-gfx] " Manasi Navare
2016-11-14 20:13 ` Cheng, Tony
2016-11-15 1:07 ` Harry Wentland
2016-11-15 1:14 ` Manasi Navare [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-15 3:13 [PATCH 0/5] Handle link training failure " Manasi Navare
2016-11-17 12:29 ` Jani Nikula
2016-11-17 19:48 ` 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=20161115011427.GA26511@intel.com \
--to=manasi.d.navare@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.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 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).