All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Marc Herbert <Marc.Herbert@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Subject: Re: [PATCH] drm/i915/dp: Improve clock recovery loop limit comment
Date: Wed, 25 Jul 2018 10:00:14 -0700	[thread overview]
Message-ID: <20180725170014.GL16907@intel.com> (raw)
In-Reply-To: <d9828548-f519-ea06-8d34-c42ad36136be@intel.com>

On Tue, Jul 24, 2018 at 05:17:53PM -0700, Marc Herbert wrote:
> Reviewed-by: Marc Herbert <marc.herbert@intel.com>

pushed, thanks.

> 
> Thx Nathan, I think this helps. I'm still curious how training normally
> converges much faster than the total number of possibilities but - unlike
> this latest clarification below - I expect the spec(s) to document that.
> 
> 
> On 24/07/2018 15:33, Nathan Ciobanu wrote:
> > Clarifies the clock recovery loop limit comment that 80
> > max_cr_tries for pre-DP1.4 devices was chosen as a very
> > tolerant upper bound.
> > Assumptions made:
> > - DP1.4 syncs should be smarter so they won't need more
> > than 10 tries
> > - pre-DP1.4 syncs should be compliant enough to not need
> > that many tries (80) but we should tolerate any that may
> > trigger this corner case
> > 
> > Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Cc: Marc Herbert <marc.herbert@intel.com>
> > Suggested-by: Marc Herbert <marc.herbert@intel.com>
> > Signed-off-by: Nathan Ciobanu <nathan.d.ciobanu@linux.intel.com>
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_dp_link_training.c b/drivers/gpu/drm/i915/intel_dp_link_training.c
> > index 07e128c7443c..a9f40985a621 100644
> > --- a/drivers/gpu/drm/i915/intel_dp_link_training.c
> > +++ b/drivers/gpu/drm/i915/intel_dp_link_training.c
> > @@ -172,10 +172,12 @@ static bool intel_dp_link_max_vswing_reached(struct intel_dp *intel_dp)
> >  	}
> >  
> >  	/*
> > -	 * DP 1.4 spec clock recovery retries defined but
> > -	 * for devices pre-DP 1.4 we set the retry limit
> > -	 * to 4 (voltage levels) x 4 (preemphasis levels) x
> > -	 * x 5 (same voltage retries) = 80 (max iterations)
> > +	 * The DP 1.4 spec defines the max clock recovery retries value
> > +	 * as 10 but for pre-DP 1.4 devices we set a very tolerant
> > +	 * retry limit of 80 (4 voltage levels x 4 preemphasis levels x
> > +	 * x 5 identical voltage retries). Since the previous specs didn't
> > +	 * define a limit and created the possibility of an infinite loop
> > +	 * we want to prevent any sync from triggering that corner case.
> >  	 */
> >  	if (intel_dp->dpcd[DP_DPCD_REV] >= DP_DPCD_REV_14)
> >  		max_cr_tries = 10;
> > 
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-07-25 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 22:33 [PATCH] drm/i915/dp: Improve clock recovery loop limit comment Nathan Ciobanu
2018-07-24 23:17 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-07-25  0:17 ` [PATCH] " Marc Herbert
2018-07-25 17:00   ` Rodrigo Vivi [this message]
2018-07-25  0:45 ` ✗ Fi.CI.IGT: failure for " Patchwork

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=20180725170014.GL16907@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=Marc.Herbert@intel.com \
    --cc=dhinakaran.pandiyan@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.