All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kahola <mika.kahola@intel.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5 2/2] drm/i915: Check DP no aux transaction bit on link training
Date: Tue, 05 Jan 2016 13:45:30 +0200	[thread overview]
Message-ID: <1451994330.4104.1.camel@sorvi> (raw)
In-Reply-To: <20160104172754.GC29079@ulmo>

On Mon, 2016-01-04 at 18:27 +0100, Thierry Reding wrote:
> On Tue, Dec 22, 2015 at 04:53:41PM +0100, Lukas Wunner wrote:
> > Hi Mika,
> > 
> > On Mon, Dec 21, 2015 at 01:39:15PM +0200, Mika Kahola wrote:
> > > Check if no AUX transactions are required on DP link training.
> > > If this bit is set, we can reuse the known good drive current
> > > and pre-emphasis level from the last "full" link training.
> 
> The commit message here isn't entirely accurate. You still need AUX
> transactions to configure the link according to the values obtained
> from the last full training sequence.
> 
> Thierry

Thanks Thierry! I need to rephrase the commit message.

Cheers,
Mika

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-01-05 11:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 11:39 [PATCH v5 0/2] drm/i915: Disable link training optimization if DP config has changed Mika Kahola
2015-12-21 11:39 ` [PATCH v5 1/2] drm/i915: Disable fast link training if DP config changes Mika Kahola
2015-12-21 11:39 ` [PATCH v5 2/2] drm/i915: Check DP no aux transaction bit on link training Mika Kahola
2015-12-22 15:53   ` Lukas Wunner
2015-12-23 10:07     ` Jani Nikula
2015-12-23 12:30     ` Mika Kahola
2016-01-04 17:27     ` Thierry Reding
2016-01-05 11:45       ` Mika Kahola [this message]
2015-12-21 12:14 ` ✗ warning: Fi.CI.BAT Patchwork
2015-12-21 12:14 ` Patchwork
2015-12-21 12:20 ` 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=1451994330.4104.1.camel@sorvi \
    --to=mika.kahola@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=thierry.reding@gmail.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.