All of lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>,
	intel-gfx@lists.freedesktop.org,
	Akash Goel <akash.goel@intel.com>
Subject: Re: [PATCH 1/1] drm/i915/bxt: Set time interval unit to 0.833us
Date: Wed, 07 Oct 2015 16:35:51 +0300	[thread overview]
Message-ID: <1444224951.9814.17.camel@intel.com> (raw)
In-Reply-To: <20151007132901.GB3383@phenom.ffwll.local>

On ke, 2015-10-07 at 15:29 +0200, Daniel Vetter wrote:
> On Tue, Oct 06, 2015 at 09:16:28PM +0300, Imre Deak wrote:
> > On pe, 2015-09-18 at 23:39 +0530, Sagar Arun Kamble wrote:
> > > From: Akash Goel <akash.goel@intel.com>
> > > 
> > > Signed-off-by: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
> > > Signed-off-by: Akash Goel <akash.goel@intel.com>
> > > Signed-off-by: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> > 
> > The comment about units in gen6_set_rps_thresholds() is outdated, so you
> > could update that while at it. In any case this looks ok, so:
> > Reviewed-by: Imre Deak <imre.deak@intel.com>
> 
> In your previous review you noticed that Bspec is still outdated. Has that
> been fixed meanwhile?

Yep, Sagar pointed to a page in BSpec where the relevant clocks are
defined ("Timestamp bases") and he also filed a change request in Bspec
now to update the register description itself accordingly. Should've
mentioned this when adding my r-b.

--Imre

> -Daniel
> 
> > 
> > > ---
> > >  drivers/gpu/drm/i915/i915_reg.h | 5 ++++-
> > >  1 file changed, 4 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> > > index 67bf205..6b1998c 100644
> > > --- a/drivers/gpu/drm/i915/i915_reg.h
> > > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > > @@ -2802,8 +2802,11 @@ enum skl_disp_power_wells {
> > >  
> > >  #define INTERVAL_1_28_US(us)	(((us) * 100) >> 7)
> > >  #define INTERVAL_1_33_US(us)	(((us) * 3)   >> 2)
> > > +#define INTERVAL_0_833_US(us)	(((us) * 6) / 5)
> > >  #define GT_INTERVAL_FROM_US(dev_priv, us) (IS_GEN9(dev_priv) ? \
> > > -				INTERVAL_1_33_US(us) : \
> > > +				(IS_BROXTON(dev_priv) ? \
> > > +				INTERVAL_0_833_US(us) : \
> > > +				INTERVAL_1_33_US(us)) : \
> > >  				INTERVAL_1_28_US(us))
> > >  
> > >  /*
> > 
> > 
> > _______________________________________________
> > 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-10-07 13:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18 18:09 [PATCH 1/1] drm/i915/bxt: Set time interval unit to 0.833us Sagar Arun Kamble
2015-09-21 12:39 ` Imre Deak
2015-10-06 18:16 ` Imre Deak
2015-10-07 13:29   ` Daniel Vetter
2015-10-07 13:35     ` Imre Deak [this message]
2015-10-07 14:07       ` Daniel Vetter

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=1444224951.9814.17.camel@intel.com \
    --to=imre.deak@intel.com \
    --cc=akash.goel@intel.com \
    --cc=ankitprasad.r.sharma@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.