public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/vlv: add VLV specific clock_get function v3
Date: Wed, 25 Sep 2013 10:38:33 -0700	[thread overview]
Message-ID: <20130925103833.7ee23acb@jbarnes-desktop> (raw)
In-Reply-To: <20130923180144.GV4531@intel.com>

On Mon, 23 Sep 2013 21:01:44 +0300
Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:

> On Fri, Sep 20, 2013 at 11:29:32AM -0700, Jesse Barnes wrote:
> > Calculation is a little different than other platforms.
> > 
> > v2: update to use port_clock instead
> >     rebase on top of Ville's changes
> > v3: update to new port_clock semantics - don't divide by
> >     pixel_multiplier (Ville)
> > 
> > References: https://bugs.freedesktop.org/show_bug.cgi?id=67345
> > Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> > ---
> >  drivers/gpu/drm/i915/intel_display.c |   33 ++++++++++++++++++++++++++++++++-
> >  1 file changed, 32 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > index 7eecf37..e5c9c1c 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -5048,6 +5048,34 @@ static void i9xx_get_pfit_config(struct intel_crtc *crtc,
> >  			I915_READ(LVDS) & LVDS_BORDER_ENABLE;
> >  }
> >  
> > +static void vlv_crtc_clock_get(struct intel_crtc *crtc,
> > +			       struct intel_crtc_config *pipe_config)
> > +{
> > +	struct drm_device *dev = crtc->base.dev;
> > +	struct drm_i915_private *dev_priv = dev->dev_private;
> > +	int pipe = pipe_config->cpu_transcoder;
> > +	intel_clock_t clock;
> > +	u32 mdiv;
> > +	int refclk = 100000, fastclk, update_rate;
> > +
> > +	mutex_lock(&dev_priv->dpio_lock);
> > +	mdiv = vlv_dpio_read(dev_priv, pipe, DPIO_DIV(pipe));
> > +	mutex_unlock(&dev_priv->dpio_lock);
> > +
> > +	clock.m1 = (mdiv >> DPIO_M1DIV_SHIFT) & 7;
> > +	clock.m2 = mdiv & DPIO_M2DIV_MASK;
> > +	clock.n = (mdiv >> DPIO_N_SHIFT) & 0xf;
> > +	clock.p1 = (mdiv >> DPIO_P1_SHIFT) & 7;
> > +	clock.p2 = (mdiv >> DPIO_P2_SHIFT) & 0x1f;
> > +
> > +	update_rate = refclk / clock.n;
> > +	clock.vco = update_rate * clock.m1 * clock.m2;
> > +	fastclk = clock.vco / clock.p1 / clock.p2;
> > +	clock.dot = (2 * fastclk);
> > +
> > +	pipe_config->port_clock = clock.dot / 10;
> 
> Looks like it should get roughly the right answer, but I don't see much
> point in all the intermediate results.
> 
> If you want to keep some of them for clarity, then I think this should
> be enough:
> 
> clock.vco = refclk * clock.m / clock.n;
> clock.dot = clock.vco / clock.p; /* fast clock */
> pipe_config->port_clock = clock.dot / 5;
> 
> Although calling the fast clock "dot" is a bit wrong, but I think it's
> fine here, especially as it matches what I have in mind for
> vlv_find_best_dpll(). I had to rewrite that sucker a bit to make it
> compatible with my brain ;) I'll send a patch for that ASAP.

The other advantage of having it all spelled out like this is that it
matches the freq calculation spreadsheet I sourced it from.

So I'd prefer to keep this as is, if I can have your r-b anyway. :)

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2013-09-25 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 17:28 [PATCH] drm/i915/vlv: add VLV specific clock_get function v2 Jesse Barnes
2013-09-20 18:29 ` [PATCH] drm/i915/vlv: add VLV specific clock_get function v3 Jesse Barnes
2013-09-23 18:01   ` Ville Syrjälä
2013-09-25 17:38     ` Jesse Barnes [this message]
2013-09-25 21:00       ` Daniel Vetter
2013-09-25 21:48         ` Chris Wilson

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=20130925103833.7ee23acb@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --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