From: Thierry Reding <thierry.reding@gmail.com>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/7] drm: Renaming DP training vswing pre emph defines
Date: Wed, 27 Aug 2014 15:09:05 +0200 [thread overview]
Message-ID: <20140827130904.GH23186@ulmo> (raw)
In-Reply-To: <20140827075135.GD6174@strange.amr.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1415 bytes --]
On Wed, Aug 27, 2014 at 08:51:35AM +0100, Damien Lespiau wrote:
> On Wed, Aug 27, 2014 at 08:47:54AM +0100, Damien Lespiau wrote:
> > > An alternative would be to provide a second set of defines for eDP 1.4
> > > where the name implies the meaning and then use them as appropriate.
> >
> > We went through the idea as well and:
> >
> > I actually think the nominal voltage swing and pre-emph values are quite
> > misleading. The hw is free to implement a wildly different set of voltage
> > swing/pre-emph values.
> >
> > eDP 1.4 changes those nominal values as described in the cover letter,
> > but there again, the actual hw implementation can choose fairly
> > different values than the nominal ones.
> >
> > Also, the DP 1.2 spec documents this field as (see address 103h):
> >
> > TRAINING_LANE0_SET : Link Training Control_Lane0
> > Bits 1:0 = VOLTAGE SWING SET
> > 00 –Voltage swing level 0
> > 01 –Voltage swing level 1
> > 10 –Voltage swing level 2
> > 11 –Voltage swing level 3
> >
> > So, in that sense, we're closer to the latest spec with those LEVEL_X
> > defines.
>
> I forgot to mention here that if we have separate defines for eDP 1.4,
> then we lose the possibility to share training code with big DP and eDP
> 1.3, not something desirable.
Yeah, I'd like to see the training sequences extracted into common
helpers.
Thierry
[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-08-27 13:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 10:53 [PATCH v2 0/7] Rename DP training vswing/pre-emph defines sonika.jindal
2014-08-08 10:53 ` [PATCH 1/7] drm: Renaming DP training vswing pre emph defines sonika.jindal
2014-08-11 16:59 ` [Intel-gfx] " Damien Lespiau
2014-08-26 11:28 ` Thierry Reding
2014-08-27 4:31 ` Jindal, Sonika
2014-08-28 0:34 ` Jingoo Han
2014-08-27 7:47 ` Damien Lespiau
2014-08-27 7:51 ` Damien Lespiau
2014-08-27 13:09 ` Thierry Reding [this message]
2014-08-27 13:11 ` Thierry Reding
2014-08-28 7:01 ` Damien Lespiau
2014-08-08 10:53 ` [PATCH 2/7] drm/i915: " sonika.jindal
2014-08-11 17:04 ` Damien Lespiau
2014-08-08 10:53 ` [PATCH 3/7] drm/exynos: " sonika.jindal
2014-08-28 0:55 ` Jingoo Han
2014-08-28 4:32 ` Jindal, Sonika
2014-08-28 6:06 ` Jingoo Han
2014-08-28 6:11 ` Jindal, Sonika
2014-08-08 10:53 ` [PATCH 4/7] drm/gma500: " sonika.jindal
2014-08-08 10:53 ` [PATCH 5/7] drm/radeon: " sonika.jindal
2014-08-08 10:53 ` [PATCH 6/7] drm/tegra: " sonika.jindal
2014-08-08 10:53 ` [PATCH 7/7] drm: Remove old defines for vswing and pre-emph values sonika.jindal
2014-08-19 8:12 ` [PATCH v2 0/7] Rename DP training vswing/pre-emph defines Jindal, Sonika
2014-08-25 12:55 ` [Intel-gfx] " Daniel Vetter
2014-08-27 6:08 ` Jindal, Sonika
2014-08-27 13:44 ` [Intel-gfx] " Deucher, Alexander
2014-09-02 20:46 ` Daniel Vetter
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=20140827130904.GH23186@ulmo \
--to=thierry.reding@gmail.com \
--cc=damien.lespiau@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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