From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: clinton.a.taylor@intel.com
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915/chv: Remove DPIO force latency causing interpair skew issue
Date: Fri, 10 Apr 2015 13:54:10 +0300 [thread overview]
Message-ID: <20150410105410.GW17410@intel.com> (raw)
In-Reply-To: <1428612126-4634-1-git-send-email-clinton.a.taylor@intel.com>
On Thu, Apr 09, 2015 at 01:42:06PM -0700, clinton.a.taylor@intel.com wrote:
> From: Clint Taylor <clinton.a.taylor@intel.com>
>
> Latest version of the "CHV DPIO programming notes" no longer requires writes
> to TX DW 11 to fix a +2UI interpair skew issue. The current code from
> April 2014 was actually causing additional skew issues between all
> TMDS pairs.
>
> ver2: added same treatment to intel_dp.c based on Ville's testing.
>
> Cc: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= <ville.syrjala@linux.intel.com>
> Signed-off-by: Clint Taylor <clinton.a.taylor@intel.com>
Yep this fixes the DP link training issues on both of the problematic
displays I have (HP ZR24w and ASUS PB278Q). Nice work.
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Tested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_dp.c | 5 -----
> drivers/gpu/drm/i915/intel_hdmi.c | 5 -----
> 2 files changed, 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index 1b87969..f106763 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -2740,11 +2740,6 @@ static void chv_pre_enable_dp(struct intel_encoder *encoder)
>
> /* Program Tx lane latency optimal setting*/
> for (i = 0; i < 4; i++) {
> - /* Set the latency optimal bit */
> - data = (i == 1) ? 0x0 : 0x6;
> - vlv_dpio_write(dev_priv, pipe, CHV_TX_DW11(ch, i),
> - data << DPIO_FRC_LATENCY_SHFIT);
> -
> /* Set the upar bit */
> data = (i == 1) ? 0x0 : 0x1;
> vlv_dpio_write(dev_priv, pipe, CHV_TX_DW14(ch, i),
> diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
> index 26222e6..3cef326 100644
> --- a/drivers/gpu/drm/i915/intel_hdmi.c
> +++ b/drivers/gpu/drm/i915/intel_hdmi.c
> @@ -1515,11 +1515,6 @@ static void chv_hdmi_pre_enable(struct intel_encoder *encoder)
>
> /* Program Tx latency optimal setting */
> for (i = 0; i < 4; i++) {
> - /* Set the latency optimal bit */
> - data = (i == 1) ? 0x0 : 0x6;
> - vlv_dpio_write(dev_priv, pipe, CHV_TX_DW11(ch, i),
> - data << DPIO_FRC_LATENCY_SHFIT);
> -
> /* Set the upar bit */
> data = (i == 1) ? 0x0 : 0x1;
> vlv_dpio_write(dev_priv, pipe, CHV_TX_DW14(ch, i),
> --
> 1.7.9.5
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-04-10 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 17:17 [PATCH] drm/i915/chv: Remove DPIO force latency causing interpair skew issue clinton.a.taylor
2015-04-09 20:20 ` Ville Syrjälä
2015-04-09 21:01 ` Clint Taylor
2015-04-09 20:42 ` [PATCH v2] " clinton.a.taylor
2015-04-10 10:54 ` Ville Syrjälä [this message]
2015-04-10 11:34 ` Jani Nikula
2015-04-10 22:21 ` shuang.he
2015-04-13 11:04 ` Jani Nikula
2015-04-13 12:31 ` Daniel Vetter
2015-04-10 17:50 ` [PATCH] " shuang.he
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=20150410105410.GW17410@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=clinton.a.taylor@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox