All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clint Taylor <clinton.a.taylor@intel.com>
To: ville.syrjala@linux.intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: Bump CHV PFI credits to 63 when cdclk>=czclk
Date: Fri, 12 Jun 2015 09:24:24 -0700	[thread overview]
Message-ID: <557B07B8.4060107@intel.com> (raw)
In-Reply-To: <1432660960-8979-4-git-send-email-ville.syrjala@linux.intel.com>

On 05/26/2015 10:22 AM, ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Switch from using 31 PFI credits to 63 PFI credits when cdclk>=czclk on
> CHV. The spec lists both 31 and 63 as "suggested" values, but based on
> feedback from hardware folks we should actually be using 63. Originally
> I picked the 31 basically by flipping a coin.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>   drivers/gpu/drm/i915/intel_display.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 067b1de..44b9c54 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -5986,7 +5986,7 @@ static void vlv_program_pfi_credits(struct drm_i915_private *dev_priv)
>   	if (DIV_ROUND_CLOSEST(dev_priv->cdclk_freq, 1000) >= dev_priv->rps.cz_freq) {
>   		/* CHV suggested value is 31 or 63 */
>   		if (IS_CHERRYVIEW(dev_priv))
> -			credits = PFI_CREDIT_31;
> +			credits = PFI_CREDIT_63;
>   		else
>   			credits = PFI_CREDIT(15);
>   	} else {
>

Although not part of this review the else clause is setting PFI_CREDIT 
to 15 when the BPSEC states that the default of 8 should be used when 
cdclk/czclk < 1. According to the original patch, 15 is the optimal 
value as stated by another driver team.

Reviewed-by: Clint Taylor <Clinton.A.Taylor@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-06-12 16:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 17:22 [PATCH 0/3] drm/i915: CHV DPIO and PFI stuff ville.syrjala
2015-05-26 17:22 ` [PATCH 1/3] drm/i915: Use the default 600ns LDO programming sequence delay ville.syrjala
2015-05-26 17:22 ` [PATCH 2/3] drm/i915: Throw out WIP CHV power well definitions ville.syrjala
2015-05-27 12:06   ` Daniel Vetter
2015-05-28  6:29     ` Ville Syrjälä
2015-05-26 17:22 ` [PATCH 3/3] drm/i915: Bump CHV PFI credits to 63 when cdclk>=czclk ville.syrjala
2015-06-12 16:24   ` Clint Taylor [this message]
2015-06-15 10:26     ` 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=557B07B8.4060107@intel.com \
    --to=clinton.a.taylor@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@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 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.