All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	intel-gfx@lists.freedesktop.org,
	Arthur J Runyan <arthur.j.runyan@intel.com>
Subject: Re: [PATCH] drm/i915/glk: Remove 99% limitation.
Date: Fri, 26 Oct 2018 19:53:34 +0300	[thread overview]
Message-ID: <20181026165334.GB9144@intel.com> (raw)
In-Reply-To: <20181026005636.22274-1-rodrigo.vivi@intel.com>

On Thu, Oct 25, 2018 at 05:56:36PM -0700, Rodrigo Vivi wrote:
> While checking the opportunity to add a display_gen
> check to allow glk and cnl to be on same bucket I noticed
> these FIXME cases here.
> 
> So I got the confirmation from HW architect that we actually
> never needed this workaround.
> 
> "GLK supports 2 pixel per clock, so pixel clock can be up to 2 * cdclk."

Cool.

Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> 
> So, this reverts commit 97f55ca5b662 ("drm/i915/glk: limit pixel
>  clock to 99% of cdclk workaround")
> 
> Fixes: 97f55ca5b662 ("drm/i915/glk: limit pixel clock to 99% of cdclk workaround")
> 
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Madhav Chauhan <madhav.chauhan@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Clinton Taylor <clinton.a.taylor@intel.com>
> Cc: Arthur J Runyan <arthur.j.runyan@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_cdclk.c | 18 ++----------------
>  1 file changed, 2 insertions(+), 16 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_cdclk.c b/drivers/gpu/drm/i915/intel_cdclk.c
> index 29075c763428..8d74276029e6 100644
> --- a/drivers/gpu/drm/i915/intel_cdclk.c
> +++ b/drivers/gpu/drm/i915/intel_cdclk.c
> @@ -2138,16 +2138,8 @@ void intel_set_cdclk(struct drm_i915_private *dev_priv,
>  static int intel_pixel_rate_to_cdclk(struct drm_i915_private *dev_priv,
>  				     int pixel_rate)
>  {
> -	if (INTEL_GEN(dev_priv) >= 10)
> +	if (INTEL_GEN(dev_priv) >= 10 || IS_GEMINILAKE(dev_priv))
>  		return DIV_ROUND_UP(pixel_rate, 2);
> -	else if (IS_GEMINILAKE(dev_priv))
> -		/*
> -		 * FIXME: Avoid using a pixel clock that is more than 99% of the cdclk
> -		 * as a temporary workaround. Use a higher cdclk instead. (Note that
> -		 * intel_compute_max_dotclk() limits the max pixel clock to 99% of max
> -		 * cdclk.)
> -		 */
> -		return DIV_ROUND_UP(pixel_rate * 100, 2 * 99);
>  	else if (IS_GEN9(dev_priv) ||
>  		 IS_BROADWELL(dev_priv) || IS_HASWELL(dev_priv))
>  		return pixel_rate;
> @@ -2543,14 +2535,8 @@ static int intel_compute_max_dotclk(struct drm_i915_private *dev_priv)
>  {
>  	int max_cdclk_freq = dev_priv->max_cdclk_freq;
>  
> -	if (INTEL_GEN(dev_priv) >= 10)
> +	if (INTEL_GEN(dev_priv) >= 10 || IS_GEMINILAKE(dev_priv))
>  		return 2 * max_cdclk_freq;
> -	else if (IS_GEMINILAKE(dev_priv))
> -		/*
> -		 * FIXME: Limiting to 99% as a temporary workaround. See
> -		 * intel_min_cdclk() for details.
> -		 */
> -		return 2 * max_cdclk_freq * 99 / 100;
>  	else if (IS_GEN9(dev_priv) ||
>  		 IS_BROADWELL(dev_priv) || IS_HASWELL(dev_priv))
>  		return max_cdclk_freq;
> -- 
> 2.19.1

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-10-26 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26  0:56 [PATCH] drm/i915/glk: Remove 99% limitation Rodrigo Vivi
2018-10-26  1:23 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-10-26  9:35 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-10-26 16:22 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-26 16:53 ` Ville Syrjälä [this message]
2018-10-29 17:47   ` [PATCH] " Rodrigo Vivi
2018-10-26 23:35 ` ✓ Fi.CI.IGT: success for " Patchwork

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=20181026165334.GB9144@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=arthur.j.runyan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=rodrigo.vivi@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.