Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kahola <mika.kahola@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v4 04/11] drm/i915: LVDS pixel clock check
Date: Fri, 14 Aug 2015 16:24:02 +0300	[thread overview]
Message-ID: <1439558642.3767.3.camel@sorvi> (raw)
In-Reply-To: <20150814130905.GZ5176@intel.com>

On Fri, 2015-08-14 at 16:09 +0300, Ville Syrjälä wrote:
> On Fri, Aug 14, 2015 at 01:03:24PM +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 LVDS.
> > 
> > V2:
> > - removed computation for max pixel clock
> > 
> > V3:
> > - cleanup by removing unnecessary lines
> > 
> > V4:
> > - moved supported dotclock check from mode_valid() to intel_lvds_init()
> > 
> > Signed-off-by: Mika Kahola <mika.kahola@intel.com>
> > ---
> >  drivers/gpu/drm/i915/intel_lvds.c | 15 +++++++++++----
> >  1 file changed, 11 insertions(+), 4 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_lvds.c b/drivers/gpu/drm/i915/intel_lvds.c
> > index 881b5d1..06b9d1b 100644
> > --- a/drivers/gpu/drm/i915/intel_lvds.c
> > +++ b/drivers/gpu/drm/i915/intel_lvds.c
> > @@ -1098,8 +1098,11 @@ void intel_lvds_init(struct drm_device *dev)
> >  			drm_mode_debug_printmodeline(scan);
> >  
> >  			fixed_mode = drm_mode_duplicate(dev, scan);
> > -			if (fixed_mode)
> > -				goto out;
> > +			if (fixed_mode) {
> > +				if (fixed_mode->clock <= dev_priv->max_dotclk_freq)
> > +					goto out;
> > +			}
> > +			fixed_mode = NULL;
> >  		}
> >  	}
> >  
> > @@ -1111,8 +1114,10 @@ void intel_lvds_init(struct drm_device *dev)
> >  		fixed_mode = drm_mode_duplicate(dev, dev_priv->vbt.lfp_lvds_vbt_mode);
> >  		if (fixed_mode) {
> >  			fixed_mode->type |= DRM_MODE_TYPE_PREFERRED;
> > -			goto out;
> > +			if (fixed_mode->clock <= dev_priv->max_dotclk_freq)
> > +				goto out;
> >  		}
> > +		fixed_mode = NULL;
> >  	}
> >  
> >  	/*
> > @@ -1135,8 +1140,10 @@ void intel_lvds_init(struct drm_device *dev)
> >  			DRM_DEBUG_KMS("using current (BIOS) mode: ");
> >  			drm_mode_debug_printmodeline(fixed_mode);
> >  			fixed_mode->type |= DRM_MODE_TYPE_PREFERRED;
> > -			goto out;
> > +			if (fixed_mode->clock <= dev_priv->max_dotclk_freq)
> > +				goto out;
> >  		}
> > +		fixed_mode = NULL;
> 
> I don't think we want to special case just LVDS this way. Whatever we do
> with fixed_mode validation should be done for all connector types that
> have it. For now I think we can more or less ignore the issue.
> 
> So in that light, your previous patch was OK except it should have just
> checked fixed_mode->clock instead of mode->clock. Sorry if my ramblings
> confused you too much.
> 
No worries. I was a bit unsure if this check should have been done in
init anyway. I'll take a step back and modify the previous patch.

-Mika-
> >  	}
> >  
> >  	/* If we still don't have a mode after all that, give up. */
> > -- 
> > 1.9.1
> > 
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-08-14 13:24 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 [this message]
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ä
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=1439558642.3767.3.camel@sorvi \
    --to=mika.kahola@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox