All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Mika Kahola <mika.kahola@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5 3/3] drm/i915: DP channel EQ check for use of DP link training optimization
Date: Mon, 4 Jan 2016 18:53:44 +0200	[thread overview]
Message-ID: <20160104165344.GJ4437@intel.com> (raw)
In-Reply-To: <20160104164409.GH4437@intel.com>

On Mon, Jan 04, 2016 at 06:44:09PM +0200, Ville Syrjälä wrote:
> On Mon, Jan 04, 2016 at 01:21:24PM +0200, Mika Kahola wrote:
> > Don't use DP link training optimization if channel EQ is not ok. It has
> > been reported that in case of failure in channel EQ check the link training
> > optimization can be enabled and therefore may not be able to reuse the
> > previously computed drive current and pre-emphasis levels.
> > 
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91393
> > Signed-off-by: Mika Kahola <mika.kahola@intel.com>
> > ---
> >  drivers/gpu/drm/i915/intel_dp.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> > index 3137187..0cd1ccb 100644
> > --- a/drivers/gpu/drm/i915/intel_dp.c
> > +++ b/drivers/gpu/drm/i915/intel_dp.c
> > @@ -4354,6 +4354,7 @@ intel_dp_check_link_status(struct intel_dp *intel_dp)
> >  		(!drm_dp_channel_eq_ok(link_status, intel_dp->lane_count))) {
> >  		DRM_DEBUG_KMS("%s: channel EQ not ok, retraining\n",
> >  			      intel_encoder->base.name);
> > +		intel_dp->train_set_valid = false;
> >  		intel_dp_start_link_train(intel_dp);
> >  		intel_dp_stop_link_train(intel_dp);
> >  	}
> 
> Should do the same for the MST case I suppose?

Also I wonder if we shold maintain some sort of blacklist of unstable
vswing/preemph settings so that we wouldn't even try to retrain with
values we know to be of questionable quality...

> 
> > -- 
> > 1.9.1
> 
> -- 
> Ville Syrjälä
> Intel OTC
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-01-04 16:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 11:21 [PATCH v5 0/3] drm/i915: Disable link training optimization if DP config has changed Mika Kahola
2016-01-04 11:21 ` [PATCH v5 1/3] drm/i915: Disable fast link training if DP config changes Mika Kahola
2016-01-04 16:42   ` Ville Syrjälä
2016-01-05 12:13     ` Mika Kahola
2016-01-04 11:21 ` [PATCH v5 2/3] drm/i915: Check DP no aux transaction bit on link training Mika Kahola
2016-01-04 11:21 ` [PATCH v5 3/3] drm/i915: DP channel EQ check for use of DP link training optimization Mika Kahola
2016-01-04 16:44   ` Ville Syrjälä
2016-01-04 16:53     ` Ville Syrjälä [this message]
2016-01-05 11:08       ` Mika Kahola
2016-01-11 18:28         ` Ville Syrjälä
2016-01-05  9:37     ` Mika Kahola
2016-01-04 11:49 ` ✗ warning: Fi.CI.BAT Patchwork
2016-01-04 12:11 ` [PATCH v5 0/3] drm/i915: Disable link training optimization if DP config has changed Maarten Lankhorst
2016-01-04 12:16   ` Mika Kahola

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=20160104165344.GJ4437@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kahola@intel.com \
    /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.