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 v5 4/4] drm/i915: DVO pixel clock check
Date: Fri, 21 Aug 2015 14:52:54 +0300 [thread overview]
Message-ID: <1440157974.3167.3.camel@sorvi> (raw)
In-Reply-To: <20150821105812.GB5176@intel.com>
On Fri, 2015-08-21 at 13:58 +0300, Ville Syrjälä wrote:
> On Tue, Aug 18, 2015 at 02:37:02PM +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)'
> >
> > V5:
> > - dot clock check against fixed_mode clock when available
> >
> > Signed-off-by: Mika Kahola <mika.kahola@intel.com>
>
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
Thanks Ville for the reviews!
-Mika-
> > ---
> > drivers/gpu/drm/i915/intel_dvo.c | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_dvo.c b/drivers/gpu/drm/i915/intel_dvo.c
> > index dc532bb..c80fe1f 100644
> > --- a/drivers/gpu/drm/i915/intel_dvo.c
> > +++ b/drivers/gpu/drm/i915/intel_dvo.c
> > @@ -201,6 +201,8 @@ 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;
> > + int target_clock = mode->clock;
> >
> > if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
> > return MODE_NO_DBLESCAN;
> > @@ -212,8 +214,13 @@ intel_dvo_mode_valid(struct drm_connector *connector,
> > return MODE_PANEL;
> > if (mode->vdisplay > intel_dvo->panel_fixed_mode->vdisplay)
> > return MODE_PANEL;
> > +
> > + target_clock = intel_dvo->panel_fixed_mode->clock;
> > }
> >
> > + if (target_clock > max_dotclk)
> > + return MODE_CLOCK_HIGH;
> > +
> > 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
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-08-21 11:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 11:36 [PATCH v5 0/4] Check pixel clock when setting mode Mika Kahola
2015-08-18 11:36 ` [PATCH v5 1/4] drm/i915: Store max dotclock Mika Kahola
2015-08-21 10:56 ` Ville Syrjälä
2015-08-18 11:37 ` [PATCH v5 2/4] drm/i915: LVDS pixel clock check Mika Kahola
2015-08-21 10:57 ` Ville Syrjälä
2015-08-18 11:37 ` [PATCH v5 3/4] drm/i915: DSI " Mika Kahola
2015-08-21 10:57 ` Ville Syrjälä
2015-08-18 11:37 ` [PATCH v5 4/4] drm/i915: DVO " Mika Kahola
2015-08-21 10:58 ` Ville Syrjälä
2015-08-21 11:52 ` Mika Kahola [this message]
2015-08-26 8:29 ` Daniel Vetter
2015-08-28 5:53 ` 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=1440157974.3167.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