From: Jani Nikula <jani.nikula@linux.intel.com>
To: Manasi Navare <manasi.d.navare@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: daniel.vetter@intel.com
Subject: Re: [PATCH RFC v2 0/5] Link Training Compliance support, link rate fallback sending Uevent
Date: Mon, 10 Oct 2016 16:17:47 +0300 [thread overview]
Message-ID: <87k2dgs5qc.fsf@intel.com> (raw)
In-Reply-To: <1475883169-7960-1-git-send-email-manasi.d.navare@intel.com>
On Sat, 08 Oct 2016, Manasi Navare <manasi.d.navare@intel.com> wrote:
> This adds support in the kernel to handle link training compliance
> requests and send a uevent to train at requested parameters.
> In this patch series, if the link training fails in modeset, then a
> hotplug uevent is added to a work queue and scheduled and failed link
> parameters are stored in intel_dp structure. This uevent
> gets executed after the modeset is completed and after locks are released.
> In the modeset retry, modes are validated based on lower link rate from
> the failed link rate value to prune the modes in intel_dp_mode_valid().
> The lower link rate is then used toc onfigure the pipe and link is retrained
> at this lower link rate.
>
> I have tested this with DPR-120 and the compliance tests are passing.
> The DP CTS spec is based on DP 1.2 spec and it only expects to reduce the link
> rate and train at the max lane count without reducing the lane count. Lane count
> reduction is added in DP 1.3 so Unigraf has agreed to add it to their next SW release.
> Hence I have not implemented fallback for lane count. But I can add it if you think
> we should add DP 1.3 link training algorithm.
>
> Please let me know your feedback on this. Compliance app is not required for link training
> tests and so I have tested this fallback using kernel console mode on Source DUT.
The question is, can you pass the link training tests using a userspace
that responds to hotplug uevents? I think you mentioned a timeout in the
CTS. If you're using fbdev, I think the retry modeset may happen faster
than with a regular userspace.
BR,
Jani.
>
> v2:
> * Corect the order of patches for correct dependencies
>
> Manasi Navare (4):
> drm/i915; Add a function to return index of link rate
> drm/i915: Add support for DP link training compliance
> drm/i915: Work queue for uevent
> drm/i915: Link Rate fallback on Link training failure
>
> Navare, Manasi D (1):
> drm/i915: Change the placement of some static functions in intel_dp.c
>
> drivers/gpu/drm/i915/i915_drv.h | 2 +
> drivers/gpu/drm/i915/intel_ddi.c | 10 +-
> drivers/gpu/drm/i915/intel_dp.c | 277 ++++++++++++++++++--------
> drivers/gpu/drm/i915/intel_dp_link_training.c | 12 +-
> drivers/gpu/drm/i915/intel_drv.h | 8 +-
> 5 files changed, 217 insertions(+), 92 deletions(-)
--
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-10-10 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 23:32 [PATCH RFC v2 0/5] Link Training Compliance support, link rate fallback sending Uevent Manasi Navare
2016-10-07 23:32 ` [PATCH RFC v2 1/5] drm/i915: Change the placement of some static functions in intel_dp.c Manasi Navare
2016-10-07 23:32 ` [PATCH RFC v2 2/5] drm/i915; Add a function to return index of link rate Manasi Navare
2016-10-07 23:32 ` [PATCH RFC v2 3/5] drm/i915: Add support for DP link training compliance Manasi Navare
2016-10-07 23:32 ` [PATCH RFC v2 4/5] drm/i915: Work queue for uevent Manasi Navare
2016-10-07 23:32 ` [PATCH RFC v2 5/5] drm/i915: Link Rate fallback on Link training failure Manasi Navare
2016-10-10 13:17 ` Jani Nikula [this message]
2016-10-10 14:20 ` ✗ Fi.CI.BAT: warning for Link Training Compliance support, link rate fallback sending Uevent (rev2) Patchwork
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=87k2dgs5qc.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=manasi.d.navare@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 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.