public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/i915: Disable fast link training if DP config changes
Date: Wed, 16 Dec 2015 15:53:43 +0200	[thread overview]
Message-ID: <20151216135343.GC4437@intel.com> (raw)
In-Reply-To: <20151216134951.GO30437@phenom.ffwll.local>

On Wed, Dec 16, 2015 at 02:49:51PM +0100, Daniel Vetter wrote:
> On Wed, Dec 16, 2015 at 03:04:47PM +0200, Mika Kahola wrote:
> > On Wed, 2015-12-16 at 14:41 +0200, Ville Syrjälä wrote:
> > > On Wed, Dec 16, 2015 at 02:26:58PM +0200, Mika Kahola wrote:
> > > > Disable DP fast link training if DP link configuration
> > > > changes. If one of the DP link parameters i.e. link
> > > > bandwidth, lane count, rate selection, port clock or bpp
> > > > changes the link training does no longer apply the
> > > > previously computed voltage swing and pre-emphasis values.
> > > > Instead, the link training is started with zero values.
> > > > 
> > > > v3: Remove cached old link parameters. Instead, disable
> > > >     fast link training feature when link parameters are
> > > >     set (Ville)
> > > > 
> > > > v2: Readout DPCD register to check if no aux handshaking is
> > > >     required in link training (Ander)
> > > > 
> > > > Signed-off-by: Mika Kahola <mika.kahola@intel.com>
> > > > ---
> > > >  drivers/gpu/drm/i915/intel_dp.c               |  3 ++-
> > > >  drivers/gpu/drm/i915/intel_dp_link_training.c | 16 ++++++++++++++++
> > > >  drivers/gpu/drm/i915/intel_drv.h              |  1 +
> > > >  3 files changed, 19 insertions(+), 1 deletion(-)
> > > > 
> > > > diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> > > > index 31ba241..92adf21 100644
> > > > --- a/drivers/gpu/drm/i915/intel_dp.c
> > > > +++ b/drivers/gpu/drm/i915/intel_dp.c
> > > > @@ -1679,6 +1679,7 @@ void intel_dp_set_link_params(struct intel_dp *intel_dp,
> > > >  {
> > > >  	intel_dp->link_rate = pipe_config->port_clock;
> > > >  	intel_dp->lane_count = pipe_config->lane_count;
> > > > +	intel_dp->train_set_valid = false;
> > > 
> > > This would disable the optimization every time we fire up the link.
> > > You would have to check the new vs. current params first, and clear
> > > the flag only if there's a difference.
> > Yeah, you're right. A step too far..
> 
> Or should we clear in the detection code upon hotplug? Lane reversal, usb
> type C and stuff like that need to probe the link in there too.

We already clear it on long hpd.

-- 
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:[~2015-12-16 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16 12:26 [PATCH v3] drm/i915: Disable fast link training if DP config changes Mika Kahola
2015-12-16 12:41 ` Ville Syrjälä
2015-12-16 13:04   ` Mika Kahola
2015-12-16 13:49     ` Daniel Vetter
2015-12-16 13:53       ` Ville Syrjälä [this message]

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=20151216135343.GC4437@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --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