From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915/chv: Remove DPIO force latency causing interpair skew issue
Date: Mon, 13 Apr 2015 14:31:55 +0200 [thread overview]
Message-ID: <20150413123155.GW6092@phenom.ffwll.local> (raw)
In-Reply-To: <877ftgqog4.fsf@intel.com>
On Mon, Apr 13, 2015 at 02:04:27PM +0300, Jani Nikula wrote:
> On Sat, 11 Apr 2015, shuang.he@intel.com wrote:
> > Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
> > Task id: 6167
> > -------------------------------------Summary-------------------------------------
> > Platform Delta drm-intel-nightly Series Applied
> > PNV 276/276 276/276
> > ILK 302/302 302/302
> > SNB -31 313/313 282/313
>
> The patch does not touch SNB code paths, what gives?
In the past few days dp link retraining sprung up all over the place in
PRTS results. I dunno what exactly is happening. I think He Shuang is
still investigating.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
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-13 12:29 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ä
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 [this message]
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=20150413123155.GW6092@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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