public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ben Widawsky <benjamin.widawsky@intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
	Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH] [v3] drm/i915: Clean up the ring scaling calculations
Date: Wed, 2 Oct 2013 09:36:04 -0700	[thread overview]
Message-ID: <20131002093604.29581a01@jbarnes-t420> (raw)
In-Reply-To: <1380731102-17393-1-git-send-email-benjamin.widawsky@intel.com>

On Wed,  2 Oct 2013 09:25:02 -0700
Ben Widawsky <benjamin.widawsky@intel.com> wrote:

> This patch attempts to clean up the ring/IA scaling programming in the
> following ways.
> 1. Fix the comment about the DDR frequency. The math is 266MHz, not
> 133MHz. Formula was right, docs are wrong.
> 
> 2. Mask the DCLK register since I don't know how it is defined on future
> platforms.
> 
> 3. use mult_frac instead of magic math.
> 
> This helps for future platform enabling.
> 
> v2: Actually use the right patch. The v1 was a mix of things, none of
> which was right. Note that due to rounding, we actually get different
> values (slightly higher) for the effective ring frequency.
> 
> v3: Use 1.25 instead of 1.33 as the original code did. (Jesse)
> 
> CC: Jesse Barnes <jbarnes@virtuousgeek.org>
> CC: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> ---
>  drivers/gpu/drm/i915/intel_pm.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> index 698257c..9753bd9 100644
> --- a/drivers/gpu/drm/i915/intel_pm.c
> +++ b/drivers/gpu/drm/i915/intel_pm.c
> @@ -3663,9 +3663,9 @@ void gen6_update_ring_freq(struct drm_device *dev)
>  	/* Convert from kHz to MHz */
>  	max_ia_freq /= 1000;
>  
> -	min_ring_freq = I915_READ(MCHBAR_MIRROR_BASE_SNB + DCLK);
> -	/* convert DDR frequency from units of 133.3MHz to bandwidth */
> -	min_ring_freq = (2 * 4 * min_ring_freq + 2) / 3;
> +	min_ring_freq = I915_READ(MCHBAR_MIRROR_BASE_SNB + DCLK) & 0xf;
> +	/* convert DDR frequency from units of 266.6MHz to bandwidth */
> +	min_ring_freq = mult_frac(min_ring_freq, 8, 3);
>  
>  	/*
>  	 * For each potential GPU frequency, load a ring frequency we'd like
> @@ -3678,7 +3678,7 @@ void gen6_update_ring_freq(struct drm_device *dev)
>  		unsigned int ia_freq = 0, ring_freq = 0;
>  
>  		if (IS_HASWELL(dev)) {
> -			ring_freq = (gpu_freq * 5 + 3) / 4;
> +			ring_freq = mult_frac(gpu_freq, 5, 4);
>  			ring_freq = max(min_ring_freq, ring_freq);
>  			/* leave ia_freq as the default, chosen by cpufreq */
>  		} else {

Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>

  reply	other threads:[~2013-10-02 16:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01 19:53 [PATCH] drm/i915: Clean up the ring scaling calculations Ben Widawsky
2013-10-01 22:32 ` [PATCH] [v2] " Ben Widawsky
2013-10-02 16:19   ` Jesse Barnes
2013-10-02 16:25   ` [PATCH] [v3] " Ben Widawsky
2013-10-02 16:36     ` Jesse Barnes [this message]
2013-10-02 16:56       ` Daniel Vetter
2013-10-02 17:05     ` Chris Wilson

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=20131002093604.29581a01@jbarnes-t420 \
    --to=jbarnes@virtuousgeek.org \
    --cc=ben@bwidawsk.net \
    --cc=benjamin.widawsky@intel.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