public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Mika Kahola <mika.kahola@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3 01/11] drm/i915: Store max dotclock
Date: Wed, 12 Aug 2015 20:30:23 +0300	[thread overview]
Message-ID: <20150812173023.GC5176@intel.com> (raw)
In-Reply-To: <1438344840-3490-2-git-send-email-mika.kahola@intel.com>

On Fri, Jul 31, 2015 at 03:13:50PM +0300, Mika Kahola wrote:
> Store max dotclock into dev_priv structure so we are able
> to filter out the modes that are not supported by our
> platforms.
> 
> V2:
> - limit the max dot clock frequency to max CD clock frequency
>   for the gen9 and above
> - limit the max dot clock frequency to 90% of the max CD clock
>   frequency for the older gens
> - for Cherryview the max dot clock frequency is limited to 95%
>   of the max CD clock frequency
> - for gen2 and gen3 the max dot clock limit is set to 90% of the
>   2X max CD clock frequency
> 
> Signed-off-by: Mika Kahola <mika.kahola@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_drv.h      |  1 +
>  drivers/gpu/drm/i915/intel_display.c | 19 +++++++++++++++++++
>  2 files changed, 20 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index 04aa34a..1f69211b 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -1777,6 +1777,7 @@ struct drm_i915_private {
>  	unsigned int fsb_freq, mem_freq, is_ddr3;
>  	unsigned int skl_boot_cdclk;
>  	unsigned int cdclk_freq, max_cdclk_freq;
> +	unsigned int max_dotclk;

nit: maybe max_dotclk_freq for extra consistentcy?

>  	unsigned int hpll_freq;
>  
>  	/**
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 43b0f17..c9c6d19 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -5259,6 +5259,23 @@ static void modeset_update_crtc_power_domains(struct drm_atomic_state *state)
>  			modeset_put_power_domains(dev_priv, put_domains[i]);
>  }
>  
> +static int intel_compute_max_dotclk(struct drm_i915_private *dev_priv)
> +{
> +	int max_cdclk_freq = dev_priv->max_cdclk_freq;
> +	int max_dotclk_freq;
> +
> +	if (INTEL_INFO(dev_priv)->gen >= 9)
> +		max_dotclk_freq = max_cdclk_freq;
> +	else if (IS_CHERRYVIEW(dev_priv))
> +		max_dotclk_freq = DIV_ROUND_UP(max_cdclk_freq * 95, 100);
> +	else if (INTEL_INFO(dev_priv)->gen == 2 || INTEL_INFO(dev_priv)->gen == 3)

intel_crtc_compute_config() uses 'gen < 4' as the condition around the
double_wide handling. Maybe do the same here for consistency.

> +		max_dotclk_freq = DIV_ROUND_UP(2 * max_cdclk_freq * 90, 100);
> +	else
> +		max_dotclk_freq = DIV_ROUND_UP(max_cdclk_freq * 90, 100);

These should round down to match what we do in the calc_cdclk funcs.

Also to add another bikeshed color, there's no need for the local
max_dotclk_freq variable, you can just 'return <whatever>' from each
branch.

With at least the rounding fixed this can have
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> +
> +	return max_dotclk_freq;
> +}
> +
>  static void intel_update_max_cdclk(struct drm_device *dev)
>  {
>  	struct drm_i915_private *dev_priv = dev->dev_private;
> @@ -5298,6 +5315,8 @@ static void intel_update_max_cdclk(struct drm_device *dev)
>  		dev_priv->max_cdclk_freq = dev_priv->cdclk_freq;
>  	}
>  
> +	dev_priv->max_dotclk = intel_compute_max_dotclk(dev_priv);
> +
>  	DRM_DEBUG_DRIVER("Max CD clock rate: %d kHz\n",
>  			 dev_priv->max_cdclk_freq);
>  }
> -- 
> 1.9.1
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

  reply	other threads:[~2015-08-12 17:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 12:13 [PATCH v3 00/11] Check pixel clock when setting mode Mika Kahola
2015-07-31 12:13 ` [PATCH v3 01/11] drm/i915: Store max dotclock Mika Kahola
2015-08-12 17:30   ` Ville Syrjälä [this message]
2015-08-12 19:01     ` Ville Syrjälä
2015-08-13  8:21       ` Mika Kahola
2015-07-31 12:13 ` [PATCH v3 02/11] drm/i915: DisplayPort pixel clock check Mika Kahola
2015-08-12 18:50   ` Ville Syrjälä
2015-07-31 12:13 ` [PATCH v3 03/11] drm/i915: HDMI " Mika Kahola
2015-08-12 18:34   ` Ville Syrjälä
2015-08-14  8:30     ` Daniel Vetter
2015-08-14 13:03       ` Ville Syrjälä
2015-08-14 13:11         ` Daniel Vetter
2015-07-31 12:13 ` [PATCH v3 04/11] drm/i915: LVDS " Mika Kahola
2015-08-12 17:40   ` Ville Syrjälä
2015-07-31 12:13 ` [PATCH v3 05/11] drm/i915: SDVO " Mika Kahola
2015-08-12 17:46   ` Ville Syrjälä
2015-07-31 12:13 ` [PATCH v3 06/11] drm/i915: DSI " Mika Kahola
2015-08-12 18:15   ` Ville Syrjälä
2015-07-31 12:13 ` [PATCH v3 07/11] drm/i915: CRT " Mika Kahola
2015-08-12 18:59   ` Ville Syrjälä
2015-07-31 12:13 ` [PATCH v3 08/11] drm/i915: TV " Mika Kahola
2015-08-12 18:24   ` Ville Syrjälä
2015-08-14  8:33     ` Daniel Vetter
2015-07-31 12:13 ` [PATCH v3 09/11] drm/i915: DisplayPort-MST " Mika Kahola
2015-08-12 18:49   ` Ville Syrjälä
2015-08-14  8:36     ` Daniel Vetter
2015-07-31 12:13 ` [PATCH v3 10/11] drm/i915: DVO " Mika Kahola
2015-08-12 18:41   ` Ville Syrjälä
2015-07-31 12:14 ` [PATCH v3 11/11] drm/i915: Max DOT clock frequency to debugfs Mika Kahola
2015-08-10 13:25   ` 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=20150812173023.GC5176@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kahola@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