Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: make DP training try a little harder
Date: Wed, 5 Jan 2011 08:40:08 -0800	[thread overview]
Message-ID: <20110105084008.76a1fdc2@jbarnes-desktop> (raw)
In-Reply-To: <0d30dc$klk0jr@orsmga001.jf.intel.com>

On Wed, 05 Jan 2011 10:43:41 +0000
Chris Wilson <chris@chris-wilson.co.uk> wrote:

> On Tue,  4 Jan 2011 11:53:14 -0800, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > When trying to do channel equalization, we need to make sure we still
> > have clock recovery on all lanes while training.  We also need to try
> > clock recovery again if we lose the clock or if channel eq fails 5
> > times.  We'll try clock recovery up to 5 more times before giving up
> > entirely.
> > 
> > Gets suspend/resume working on my Vaio again and brings us back into
> > compliance with the DP training sequence spec.
> 
> There are still ways link training can silently fail. The next task for
> the foolhardy is return error codes from modesetting (and accept that any
> failure can leave the system in a partially defined state, with a forced
> mode reset in the drm_kms_helper?).
> 
> > -		/* Try 5 times */
> > -		if (tries > 5)
> > +		/* Try 5 times, then try clock recovery if that fails */
> > +		if (tries > 5) {
> > +			intel_dp_link_down(intel_dp);
> > +			intel_dp_start_link_train(intel_dp);
> > +			tries = 0;
> > +			cr_tries++;
> >  			break;
> 
> This should be a continue, right?.

Oops, yeah the loop is wrong; the cr_tries check needs to be above the
first continue as well.  Will fix, but it sounds like it won't help
with Yuanhan's problem...

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2011-01-05 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 19:53 [PATCH] drm/i915: make DP training try a little harder Jesse Barnes
2011-01-05  7:52 ` Yuanhan Liu
2011-01-05 17:19   ` Jesse Barnes
2011-01-05 21:23     ` Jan-Hendrik Zab
2011-01-06  0:42     ` [PATCH] " Yuanhan Liu
2011-01-05 10:43 ` Chris Wilson
2011-01-05 16:40   ` Jesse Barnes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-01-05 22:45 Jesse Barnes
2011-01-06  1:56 ` Yuanhan Liu
2011-01-06 12:18 ` Chris Wilson

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=20110105084008.76a1fdc2@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=chris@chris-wilson.co.uk \
    --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