From: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>,
dri-devel@lists.freedesktop.org
Subject: [PATCH 3/4] drm/dp: Clarify clock recovery and channel equalization failures
Date: Wed, 3 Aug 2016 20:07:40 -0700 [thread overview]
Message-ID: <1470280061-640-4-git-send-email-dhinakaran.pandiyan@intel.com> (raw)
In-Reply-To: <1470280061-640-1-git-send-email-dhinakaran.pandiyan@intel.com>
The causes of clock recovery and channel equalization failures are not
explicitly printed in debug messages. Help debugging link training
failures by printing why it failed.
Doing this in the driver would mean re-implementing some of the drm static
functions that decode link status. Let's avoid that with these debug
messages in drm.
Signed-off-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
---
drivers/gpu/drm/drm_dp_helper.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/drm_dp_helper.c b/drivers/gpu/drm/drm_dp_helper.c
index 091053e..d763b57 100644
--- a/drivers/gpu/drm/drm_dp_helper.c
+++ b/drivers/gpu/drm/drm_dp_helper.c
@@ -64,12 +64,16 @@ bool drm_dp_channel_eq_ok(const u8 link_status[DP_LINK_STATUS_SIZE],
lane_align = dp_link_status(link_status,
DP_LANE_ALIGN_STATUS_UPDATED);
- if ((lane_align & DP_INTERLANE_ALIGN_DONE) == 0)
+ if ((lane_align & DP_INTERLANE_ALIGN_DONE) == 0) {
+ DRM_DEBUG_KMS("Inter-lane alignment not done\n");
return false;
+ }
for (lane = 0; lane < lane_count; lane++) {
lane_status = dp_get_lane_status(link_status, lane);
- if ((lane_status & DP_CHANNEL_EQ_BITS) != DP_CHANNEL_EQ_BITS)
+ if ((lane_status & DP_CHANNEL_EQ_BITS) != DP_CHANNEL_EQ_BITS) {
+ DRM_DEBUG_KMS("Channel equalization not done for lane %d\n", lane);
return false;
+ }
}
return true;
}
@@ -83,8 +87,10 @@ bool drm_dp_clock_recovery_ok(const u8 link_status[DP_LINK_STATUS_SIZE],
for (lane = 0; lane < lane_count; lane++) {
lane_status = dp_get_lane_status(link_status, lane);
- if ((lane_status & DP_LANE_CR_DONE) == 0)
+ if ((lane_status & DP_LANE_CR_DONE) == 0) {
+ DRM_DEBUG_KMS("Clock recovery not done for lane %d\n", lane);
return false;
+ }
}
return true;
}
--
2.5.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-04 3:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 3:07 [PATCH 0/4] Improve logging for DP link training Dhinakaran Pandiyan
2016-08-04 3:07 ` [PATCH 1/4] drm/i915/dp: Add debug messages to print DP link training pattern Dhinakaran Pandiyan
2016-08-04 3:07 ` [Intel-gfx] " Chris Wilson
2016-08-04 16:51 ` Pandiyan, Dhinakaran
2016-08-04 3:07 ` [PATCH 2/4] drm/i915/dp: Switch to using the DRM function for reading DP link status Dhinakaran Pandiyan
2016-08-04 3:11 ` Chris Wilson
2016-08-04 5:48 ` Ville Syrjälä
2016-08-04 3:07 ` Dhinakaran Pandiyan [this message]
2016-08-04 3:12 ` [PATCH 3/4] drm/dp: Clarify clock recovery and channel equalization failures Chris Wilson
2016-08-04 16:50 ` Pandiyan, Dhinakaran
2016-08-04 17:07 ` [Intel-gfx] " chris
2016-08-04 3:07 ` [PATCH 4/4] drm/i915/dp: Dump DP link status when link training stages fails Dhinakaran Pandiyan
2016-08-04 7:46 ` [Intel-gfx] " Jani Nikula
2016-08-04 16:46 ` Pandiyan, Dhinakaran
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=1470280061-640-4-git-send-email-dhinakaran.pandiyan@intel.com \
--to=dhinakaran.pandiyan@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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