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 3/3] drm/i915: Fix comments about GMBUSFREQ register
Date: Thu, 28 Apr 2016 21:40:01 +0300 [thread overview]
Message-ID: <20160428184001.GJ4329@intel.com> (raw)
In-Reply-To: <20160427135642.GK4329@intel.com>
On Wed, Apr 27, 2016 at 04:56:42PM +0300, Ville Syrjälä wrote:
> On Wed, Apr 27, 2016 at 04:30:14PM +0300, Mika Kahola wrote:
> > s/Programmng/Programming
>
> It's straight from the spec, hence the [sic]
Didn't get any further objections, so pushed the series to dinq, with the typoes
and [sic]s intact.
Thans for the reviews.
>
> >
> > With this nitpick fixed, this is
> >
> > Reviewed-by: Mika Kahola <mika.kahola@intel.com>
> >
> > On Tue, 2016-04-26 at 19:46 +0300, ville.syrjala@linux.intel.com wrote:
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > >
> > > The comment about GMBUSFREQ is confused. The spec actually explains
> > > the 4MHz thing perfectly by noting that the 4MHz divider values is
> > > actually just bits [9:2] not [9:0], hence the divide by 1000 correct.
> > > Replace the confused note with a quote from the spec, and eliminate
> > > the duplicated comment that snuck in.
> > >
> > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > ---
> > > drivers/gpu/drm/i915/intel_display.c | 15 +++++----------
> > > 1 file changed, 5 insertions(+), 10 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > > index ea55dd331fac..ec9144ded255 100644
> > > --- a/drivers/gpu/drm/i915/intel_display.c
> > > +++ b/drivers/gpu/drm/i915/intel_display.c
> > > @@ -5311,18 +5311,13 @@ static void intel_update_cdclk(struct drm_device *dev)
> > > dev_priv->cdclk_freq);
> > >
> > > /*
> > > - * Program the gmbus_freq based on the cdclk frequency.
> > > - * BSpec erroneously claims we should aim for 4MHz, but
> > > - * in fact 1MHz is the correct frequency.
> > > + * 9:0 CMBUS [sic] CDCLK frequency (cdfreq):
> > > + * Programmng [sic] note: bit[9:2] should be programmed to the number
> > > + * of cdclk that generates 4MHz reference clock freq which is used to
> > > + * generate GMBus clock. This will vary with the cdclk freq.
> > > */
> > > - if (IS_VALLEYVIEW(dev) || IS_CHERRYVIEW(dev)) {
> > > - /*
> > > - * Program the gmbus_freq based on the cdclk frequency.
> > > - * BSpec erroneously claims we should aim for 4MHz, but
> > > - * in fact 1MHz is the correct frequency.
> > > - */
> > > + if (IS_VALLEYVIEW(dev_priv) || IS_CHERRYVIEW(dev_priv))
> > > I915_WRITE(GMBUSFREQ_VLV, DIV_ROUND_UP(dev_priv->cdclk_freq, 1000));
> > > - }
> > >
> > > if (dev_priv->max_cdclk_freq == 0)
> > > intel_update_max_cdclk(dev);
> >
> > --
> > Mika Kahola - Intel OTC
>
> --
> Ville Syrjälä
> Intel OTC
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-28 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 16:46 [PATCH 0/3] drm/i915: Cdclk related fixes and polish ville.syrjala
2016-04-26 16:46 ` [PATCH 1/3] drm/i915: Update CDCLK_FREQ register on BDW after changing cdclk frequency ville.syrjala
2016-04-27 8:19 ` Mika Kahola
2016-04-27 8:19 ` Mika Kahola
2016-04-26 16:46 ` [PATCH 2/3] drm/i915: Use cached cdclk value in i915_audio_component_get_cdclk_freq() ville.syrjala
2016-04-27 13:06 ` Mika Kahola
2016-04-26 16:46 ` [PATCH 3/3] drm/i915: Fix comments about GMBUSFREQ register ville.syrjala
2016-04-27 13:30 ` Mika Kahola
2016-04-27 13:56 ` Ville Syrjälä
2016-04-28 18:40 ` Ville Syrjälä [this message]
2016-04-27 6:19 ` ✗ Fi.CI.BAT: warning for drm/i915: Cdclk related fixes and polish Patchwork
2016-04-27 17:28 ` Ville Syrjälä
2016-04-27 17:34 ` Ville Syrjälä
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=20160428184001.GJ4329@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.