public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Robert Navarro <crshman@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Increase WM memory latency values on SNB with high pixel clock
Date: Mon, 31 Mar 2014 18:29:51 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140331T202710-668@post.gmane.org> (raw)
In-Reply-To: C7E999358BBE9E45938BA940F5F5110873E0D27B@FMSMSX102.amr.corp.intel.com

Runyan, Arthur J <arthur.j.runyan <at> intel.com> writes:

> 
> Please check the DRAM configuration for the systems that fail.  The higher 
latency is more likely with
> higher tRFC which is mainly found with 8 Gbit components.
> 

What other information do we need to get this included?

The DRAM config, is this something that I have to/should check? How do I get 
this information to you?

  reply	other threads:[~2014-03-31 18:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21  9:00 [PATCH] drm/i915: Increase WM memory latency values on SNB with high pixel clock Jani Nikula
2014-03-21  9:29 ` Chris Wilson
2014-03-21 10:19 ` Daniel Vetter
2014-03-21 17:28   ` Runyan, Arthur J
2014-03-31 18:29     ` Robert Navarro [this message]
2014-04-14  9:16       ` Ville Syrjälä
2014-05-08 12:09   ` [PATCH v2] drm/i915: Increase WM memory latency values on SNB ville.syrjala
2014-05-09 15:23     ` Robert Navarro
2014-05-09 15:38       ` [PATCH v2] drm/i915: Increase WM memory latency values?on SNB Ville Syrjälä
2014-05-09 17:46         ` Robert Navarro
2014-05-09 17:54           ` Ville Syrjälä
2014-05-14  0:55             ` Robert Navarro
2014-05-15 14:18               ` Robert Navarro
2014-05-15 10:13     ` [PATCH v2] drm/i915: Increase WM memory latency values on SNB Jani Nikula
2014-05-15 10:16       ` Chris Wilson
2014-05-15 10:34         ` Jani Nikula
2014-05-15 10:45           ` Ville Syrjälä
2014-05-15 10:58             ` Jani Nikula

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=loom.20140331T202710-668@post.gmane.org \
    --to=crshman@gmail.com \
    --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