All of lore.kernel.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 v4 10/11] drm/i915: DVO pixel clock check
Date: Fri, 14 Aug 2015 16:10:27 +0300	[thread overview]
Message-ID: <20150814131027.GA5176@intel.com> (raw)
In-Reply-To: <1439546611-3191-11-git-send-email-mika.kahola@intel.com>

On Fri, Aug 14, 2015 at 01:03:30PM +0300, Mika Kahola wrote:
> It is possible the we request to have a mode that has
> higher pixel clock than our HW can support. This patch
> checks if requested pixel clock is lower than the one
> supported by the HW. The requested mode is discarded
> if we cannot support the requested pixel clock.
> 
> This patch applies to DVO.
> 
> V2:
> - removed computation for max pixel clock
> 
> V3:
> - cleanup by removing unnecessary lines
> 
> V4:
> - clock check against max dotclock moved inside 'if (fixed_mode)'
> 
> Signed-off-by: Mika Kahola <mika.kahola@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_dvo.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/intel_dvo.c b/drivers/gpu/drm/i915/intel_dvo.c
> index dc532bb..924b724 100644
> --- a/drivers/gpu/drm/i915/intel_dvo.c
> +++ b/drivers/gpu/drm/i915/intel_dvo.c
> @@ -201,6 +201,7 @@ intel_dvo_mode_valid(struct drm_connector *connector,
>  		     struct drm_display_mode *mode)
>  {
>  	struct intel_dvo *intel_dvo = intel_attached_dvo(connector);
> +	int max_dotclk = to_i915(connector->dev)->max_dotclk_freq;
>  
>  	if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
>  		return MODE_NO_DBLESCAN;
> @@ -212,6 +213,8 @@ intel_dvo_mode_valid(struct drm_connector *connector,
>  			return MODE_PANEL;
>  		if (mode->vdisplay > intel_dvo->panel_fixed_mode->vdisplay)
>  			return MODE_PANEL;
> +		if (mode->clock > max_dotclk)
> +			return MODE_CLOCK_HIGH;
>  	}

What we want here is duplicate the intel_dp.c logic exactly, ie. check
against fixed_mode->clock when it's around, otherwise check against
mode->clock.

>  
>  	return intel_dvo->dev.dev_ops->mode_valid(&intel_dvo->dev, mode);
> -- 
> 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-14 13:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 10:03 [PATCH v4 00/11] Check pixel clock when setting mode Mika Kahola
2015-08-14 10:03 ` [PATCH v4 01/11] drm/i915: Store max dotclock Mika Kahola
2015-08-14 12:55   ` Ville Syrjälä
2015-08-14 12:59     ` Mika Kahola
2015-08-14 10:03 ` [PATCH v4 02/11] drm/i915: DisplayPort pixel clock check Mika Kahola
2015-08-14 10:03 ` [PATCH v4 03/11] drm/i915: HDMI " Mika Kahola
2015-08-14 10:03 ` [PATCH v4 04/11] drm/i915: LVDS " Mika Kahola
2015-08-14 13:09   ` Ville Syrjälä
2015-08-14 13:24     ` Mika Kahola
2015-08-14 20:10   ` Lukas Wunner
2015-08-14 10:03 ` [PATCH v4 05/11] drm/i915: SDVO " Mika Kahola
2015-08-14 10:03 ` [PATCH v4 06/11] drm/i915: DSI " Mika Kahola
2015-08-14 12:57   ` Ville Syrjälä
2015-08-14 10:03 ` [PATCH v4 07/11] drm/i915: CRT " Mika Kahola
2015-08-14 10:03 ` [PATCH v4 08/11] drm/i915: TV " Mika Kahola
2015-08-14 10:03 ` [PATCH v4 09/11] drm/i915: DisplayPort-MST " Mika Kahola
2015-08-14 10:03 ` [PATCH v4 10/11] drm/i915: DVO " Mika Kahola
2015-08-14 13:10   ` Ville Syrjälä [this message]
2015-08-14 10:03 ` [PATCH v4 11/11] drm/i915: Max DOT clock frequency to debugfs Mika Kahola
2015-08-16  4:07   ` shuang.he
2015-08-14 13:13 ` [PATCH v4 00/11] Check pixel clock when setting mode Daniel Vetter
2015-08-17 10:08   ` Mika Kahola

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=20150814131027.GA5176@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 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.