From: Todd Previte <tprevite@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: Displayport Compliance Testing V3
Date: Wed, 18 Feb 2015 20:00:28 -0700 [thread overview]
Message-ID: <1424314837-32434-1-git-send-email-tprevite@gmail.com> (raw)
These are the kernel-side patches to enable Displayport compliance testing for
the i915 driver. They establish a framework and operational parameters for
compliance testing operations on the i915 driver. Structure is in place such
that more tests can be added in the near future. Combined with the userspace
application (currently being integrated into the intel-gnu-tools tree) these
patches enable the following tests:
4.2.1.1 Source DUT Retry on No-Reply During AUX Read after HPD Plug Event
4.2.1.2 Source Retry on Invalid Reply During AUX Read after HPD Plug Event
4.2.2.1 EDID Read upon HPD Plug Event
4.2.2.2 DPCD Receiver Capability Read upon HPD Plug Event
4.2.2.3 EDID Read
4.2.2.4 EDID Read Failure #1: I2C-Over-AUX NACK
4.2.2.5 EDID Read Failure #2: I2C-Over-AUX DEFER
4.2.2.6 EDID Corruption Detection
Without the user app to set the required video mode, some of these tests will
still pass. 4.2.1.1 and 4.2.1.2 do not require the user app, nor does 4.2.2.2.
Some of the others may pass with warnings about the video mode not being set
correctly, depending on your test device. Documentation for using the userspace
app and an overview of this implementation is available with the user app.
drm/i915: Add debugfs write and test param parsing functions for DP test control
drm/i915: Add new debugfs file for Displaypor compliance test control
drm/i915: Update intel_dp_hpd_pulse() to check link status for non-MST operation
drm/i915: Update intel_dp_compute_config() to handle compliance test requests
drm/i915: Update the EDID automated compliance test function
drm/i915: Add debugfs functions for Displayport compliance testing
drm/i915: Add a delay in Displayport AUX transactions for compliance testing
drm/i915: Update intel_dp_check_link_status() for Displayport compliance testing
drm/i915: Add automated testing support for Displayport compliance testing
drivers/gpu/drm/i915/i915_debugfs.c | 643 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
drivers/gpu/drm/i915/intel_dp.c | 249 ++++++++++++++++++++----
drivers/gpu/drm/i915/intel_drv.h | 18 ++
3 files changed, 870 insertions(+), 40 deletions(-)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-02-19 3:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 3:00 Todd Previte [this message]
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 ` [PATCH 3/9] drm/i915: Add a delay in Displayport AUX transactions for " Todd Previte
2015-02-19 3:00 ` [PATCH 4/9] drm/i915: Add debugfs functions for Displayport " 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
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-1-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