From: Daniel Vetter <daniel@ffwll.ch>
To: Todd Previte <tprevite@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 10/12] drm/i915: Update link training automated test function for Displayport compliance
Date: Tue, 22 Jul 2014 08:15:30 +0200 [thread overview]
Message-ID: <20140722061530.GD15237@phenom.ffwll.local> (raw)
In-Reply-To: <1405365047-6866-11-git-send-email-tprevite@gmail.com>
On Mon, Jul 14, 2014 at 12:10:45PM -0700, Todd Previte wrote:
> Implements basic link training functionality for Displayport automated compliance
> testing.
>
> Signed-off-by: Todd Previte <tprevite@gmail.com>
> ---
> drivers/gpu/drm/i915/intel_dp.c | 47 +++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 47 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index 65830e9..e4b31ad 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -3427,6 +3427,53 @@ static uint8_t
> intel_dp_autotest_link_training(struct intel_dp *intel_dp)
> {
> uint8_t test_result = DP_TEST_NAK;
> + uint8_t rxdata[2];
> + uint8_t link_status[DP_LINK_STATUS_SIZE];
> + int bytes_ret = 0;
> + struct drm_connector *connector = &intel_dp->attached_connector->base;
> + struct intel_digital_port *intel_dig_port =
> + enc_to_dig_port(&intel_dp->attached_connector->encoder->base);
> +
> + /* Read test parameters */
> + bytes_ret = drm_dp_dpcd_read(&intel_dp->aux, DP_TEST_LINK_RATE, rxdata, 2);
> +
> + /* Set link rate directly */
> + intel_dp->link_bw = rxdata[0];
> + /* Preserve 7:5 when setting lane count */
> + intel_dp->lane_count &= 0xE0;
> + intel_dp->lane_count |= rxdata[1];
This won't work - if you change the link config you need to do a full
recomputation of the modeset config and a full modeset. No, we dont (yet)
have the infrastructure for this, which is why dp is such a pain since we
can change the link config once we've decided on something :(
-Daniel
> +
> + DRM_DEBUG_KMS("Displayport: Link training testing - %d lanes @ %02x link rate\n",
> + intel_dp->lane_count, intel_dp->link_bw);
> +
> + /* Train the link */
> + intel_dp->DP = intel_dig_port->saved_port_bits |
> + DDI_BUF_CTL_ENABLE |
> + DDI_BUF_EMP_400MV_0DB_HSW;
> + intel_dp->DP |= DDI_PORT_WIDTH(intel_dp->lane_count);
> +
> + if (!intel_dp_start_link_train(intel_dp)) {
> + DRM_DEBUG_KMS("Displayport: intel_dp_start_link_train() failed\n");
> + test_result = false;
> + }
> + if (!intel_dp_complete_link_train(intel_dp)) {
> + DRM_DEBUG_KMS("Displayport: intel_dp_complete_link_train() failed\n");
> + test_result = false;
> + }
> + if (!intel_dp_stop_link_train(intel_dp)) {
> + DRM_DEBUG_KMS("Displayport: intel_dp_stop_link_train() failed\n");
> + test_result = false;
> + }
> +
> + /* Check link status for successful completion */
> + if (drm_dp_channel_eq_ok(link_status, intel_dp->lane_count))
> + test_result = true;
> +
> + if (test_result == false) {
> + /* Clear link training here */
> + intel_dp_set_idle_link_train(intel_dp);
> + }
> +
> return test_result;
> }
>
> --
> 1.9.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-07-22 6:15 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 19:10 [PATCH v2] Displayport compliance testing Todd Previte
2014-07-14 19:10 ` [PATCH 01/12] drm/i915: Add automated testing support for " Todd Previte
2014-07-21 22:09 ` Paulo Zanoni
2014-07-30 14:49 ` Paulo Zanoni
2014-07-14 19:10 ` [PATCH 02/12] drm/i915: Add a function to compute the EDID checksum for Displayport compliance Todd Previte
2014-07-21 22:28 ` Paulo Zanoni
2014-07-14 19:10 ` [PATCH 03/12] drm/i915: Add counters in the drm_dp_aux struct for I2C NACKs and DEFERs Todd Previte
2014-07-21 22:37 ` Paulo Zanoni
2014-11-04 22:17 ` [PATCH 02/10] " Todd Previte
2014-11-04 22:26 ` Daniel Vetter
2014-07-14 19:10 ` [PATCH 04/12] drm/i915: Add wrapper function for intel_crtc_set_config() Todd Previte
2014-07-21 23:34 ` Paulo Zanoni
2014-07-14 19:10 ` [PATCH 05/12] drm/i915: Add a function to get the EDID preferred mode for Displayport compliance testing Todd Previte
2014-07-21 23:41 ` Paulo Zanoni
2014-07-14 19:10 ` [PATCH 06/12] drm/i915: Add a constant and function for getting the Displayport compliance failsafe video mode Todd Previte
2014-07-21 23:42 ` Paulo Zanoni
2014-07-14 19:10 ` [PATCH 07/12] drm/i915: Update EDID automated test function for Displayport compliance Todd Previte
2014-07-29 22:37 ` Paulo Zanoni
2014-07-31 18:27 ` Todd Previte
2014-07-14 19:10 ` [PATCH 08/12] drm/i915: Improve reliability for Displayport link training Todd Previte
2014-07-30 14:07 ` Paulo Zanoni
2014-07-30 15:25 ` Daniel Vetter
2014-07-14 19:10 ` [PATCH 09/12] drm/i915: Update intel_dp_check_link_status() for Displayport compliance testing Todd Previte
2014-07-30 14:29 ` Paulo Zanoni
2014-07-14 19:10 ` [PATCH 10/12] drm/i915: Update link training automated test function for Displayport compliance Todd Previte
2014-07-22 6:15 ` Daniel Vetter [this message]
2014-07-22 20:40 ` Jesse Barnes
2014-07-22 20:44 ` Daniel Vetter
2014-07-22 21:03 ` Jesse Barnes
2014-07-14 19:10 ` [PATCH 11/12] drm/i915: Minor code clean up in intel_dp.c Todd Previte
2014-07-15 7:47 ` Daniel Vetter
2014-07-15 15:35 ` Todd Previte
2014-07-14 19:10 ` [PATCH 12/12] drm/i915: Add a delay in Displayport AUX transactions for compliance testing Todd Previte
2014-07-15 7:46 ` Daniel Vetter
2014-07-15 15:34 ` Todd Previte
2014-07-30 14:46 ` Paulo Zanoni
2014-07-22 6:41 ` [PATCH v2] Displayport " Daniel Vetter
2014-07-22 20:48 ` Jesse Barnes
2014-07-22 20:53 ` Daniel Vetter
2014-07-22 21:11 ` Jesse Barnes
2014-07-29 21:53 ` Paulo Zanoni
2014-07-30 9:31 ` Daniel Vetter
2014-07-31 18:27 ` Todd Previte
2014-07-22 20:57 ` Jesse Barnes
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=20140722061530.GD15237@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tprevite@gmail.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