From: Todd Previte <tprevite@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 3/9] drm/i915: Add a delay in Displayport AUX transactions for compliance testing
Date: Wed, 18 Feb 2015 20:00:31 -0700 [thread overview]
Message-ID: <1424314837-32434-4-git-send-email-tprevite@gmail.com> (raw)
In-Reply-To: <1424314837-32434-1-git-send-email-tprevite@gmail.com>
The Displayport Link Layer Compliance Testing Specification 1.2 rev 1.1
specifies that repeated AUX transactions after a failure (no response /
invalid response) must have a minimum delay of 400us before the resend can
occur. Tests 4.2.1.1 and 4.2.1.2 are two tests that require this specifically.
V2:
- Changed udelay() to usleep_range()
V3:
- Removed extraneous check for timeout
- Updated comment to reflect this change
Signed-off-by: Todd Previte <tprevite@gmail.com>
---
drivers/gpu/drm/i915/intel_dp.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 280ae7a..5d7b7f3 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+++ b/drivers/gpu/drm/i915/intel_dp.c
@@ -877,9 +877,15 @@ intel_dp_aux_ch(struct intel_dp *intel_dp,
DP_AUX_CH_CTL_TIME_OUT_ERROR |
DP_AUX_CH_CTL_RECEIVE_ERROR);
- if (status & (DP_AUX_CH_CTL_TIME_OUT_ERROR |
- DP_AUX_CH_CTL_RECEIVE_ERROR))
+ /* DP CTS 1.2 Core Rev 1.1, 4.2.1.1 & 4.2.1.2
+ 400us delay required for errors and timeouts
+ Timeout errors from the HW already meet this
+ requirement so skip to next iteration
+ */
+ if (status & DP_AUX_CH_CTL_RECEIVE_ERROR) {
+ usleep_range(400, 500);
continue;
+ }
if (status & DP_AUX_CH_CTL_DONE)
break;
}
--
1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-02-19 3:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 3:00 Displayport Compliance Testing V3 Todd Previte
2015-02-19 3:00 ` [PATCH 1/9] drm/i915: Add automated testing support for Displayport compliance testing Todd Previte
2015-02-19 3:00 ` [PATCH 2/9] drm/i915: Update intel_dp_check_link_status() " Todd Previte
2015-02-19 3:00 ` Todd Previte [this message]
2015-02-19 3:00 ` [PATCH 4/9] drm/i915: Add debugfs functions " Todd Previte
2015-03-09 17:57 ` Jani Nikula
2015-03-11 17:19 ` Todd Previte
2015-02-19 3:00 ` [PATCH 5/9] drm/i915: Update the EDID automated compliance test function Todd Previte
2015-02-26 17:40 ` [PATCH 5/9 V4] " Todd Previte
2015-02-19 3:00 ` [PATCH 6/9] drm/i915: Update intel_dp_compute_config() to handle compliance test requests Todd Previte
2015-02-19 3:00 ` [PATCH 7/9] drm/i915: Update intel_dp_hpd_pulse() to check link status for non-MST operation Todd Previte
2015-03-05 18:22 ` [PATCH] " Todd Previte
2015-03-06 16:34 ` Daniel Vetter
2015-03-09 15:34 ` Jesse Barnes
2015-03-09 17:29 ` Daniel Vetter
2015-03-09 19:07 ` Jesse Barnes
2015-03-09 21:04 ` Ville Syrjälä
2015-03-11 18:37 ` Jesse Barnes
2015-03-11 19:10 ` Ville Syrjälä
2015-03-11 19:38 ` Daniel Vetter
2015-02-19 3:00 ` [PATCH 8/9] drm/i915: Add new debugfs file for Displaypor compliance test control Todd Previte
2015-02-19 3:00 ` [PATCH 9/9] drm/i915: Add debugfs write and test param parsing functions for DP " Todd Previte
2015-02-19 5:55 ` shuang.he
-- strict thread matches above, loose matches on Subject: below --
2015-03-31 17:14 [intel-gfx][PATCH V4] Displayport compliance testing V4 Todd Previte
2015-03-31 17:15 ` [PATCH 3/9] drm/i915: Add a delay in Displayport AUX transactions for compliance testing Todd Previte
2015-04-01 18:23 ` Ville Syrjälä
2015-04-01 18:55 ` Todd Previte
2015-04-01 19:22 ` Ville Syrjälä
2015-04-01 19:45 ` Todd Previte
2015-04-06 23:28 ` Paulo Zanoni
2015-04-07 2:07 ` Todd Previte
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=1424314837-32434-4-git-send-email-tprevite@gmail.com \
--to=tprevite@gmail.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