From: Damien Lespiau <damien.lespiau@intel.com>
To: akash.goel@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/7] drm/i915/skl: Updated the gen6_rps_limits function
Date: Tue, 17 Feb 2015 15:10:33 +0000 [thread overview]
Message-ID: <20150217151033.GC23520@strange.ger.corp.intel.com> (raw)
In-Reply-To: <20150217150139.GA23520@strange.ger.corp.intel.com>
On Tue, Feb 17, 2015 at 03:01:39PM +0000, Damien Lespiau wrote:
> On Tue, Feb 17, 2015 at 02:44:56PM +0000, Damien Lespiau wrote:
> > On Fri, Feb 06, 2015 at 08:26:35PM +0530, akash.goel@intel.com wrote:
> > > + if (IS_GEN9(dev_priv->dev)) {
> > > + limits = (dev_priv->rps.max_freq_softlimit * GEN9_FREQ_SCALER) << 23;
> > > + if (val <= dev_priv->rps.min_freq_softlimit)
> > > + limits |= (dev_priv->rps.min_freq_softlimit * GEN9_FREQ_SCALER) << 14;
> >
> > I believe the values here are in 16.666 Mhz, the power spec I have gives
> > examples:
> > [31:23]=54d: No interrupt if already >=900MHz
> > [22:14]=18d: No interrupt if already <= 300MHz
> >
> > and 54 * 16.66.. = 900.
>
> Right, so RP_STATE_CAP is documented using 50Mhz units, so the above is
> correct. How about unifying all values for SKL to the same units (always
> 16.66 Mhz units)? that would remove some of the confusion a bit.
Right, so going to back here, that looks correct:
Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
--
Damien
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-02-17 15:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 14:56 [PATCH 0/7] Added missing changes for Turbo feature on SKL akash.goel
2015-02-06 14:56 ` [PATCH 1/7] drm/i915/skl: Added new macros akash.goel
2015-02-16 19:05 ` Damien Lespiau
2015-02-17 14:40 ` Damien Lespiau
2015-02-17 15:20 ` Goel, Akash
2015-02-17 15:26 ` Damien Lespiau
2015-02-17 15:32 ` Goel, Akash
2015-02-23 16:21 ` Daniel Vetter
2015-02-23 16:22 ` Damien Lespiau
2015-02-06 14:56 ` [PATCH 2/7] drm/i915/skl: Updated the gen6_set_rps function akash.goel
2015-02-17 14:31 ` Damien Lespiau
2015-02-17 15:08 ` Damien Lespiau
2015-02-06 14:56 ` [PATCH 3/7] drm/i915/skl: Restructured the gen6_set_rps_thresholds function akash.goel
2015-02-06 15:48 ` Chris Wilson
2015-02-09 4:51 ` Akash Goel
2015-02-06 14:56 ` [PATCH 4/7] drm/i915/skl: Updated the gen6_rps_limits function akash.goel
2015-02-06 15:43 ` Chris Wilson
2015-02-09 4:56 ` Akash Goel
2015-02-09 11:03 ` Chris Wilson
2015-02-09 11:33 ` Akash Goel
2015-02-17 14:44 ` Damien Lespiau
2015-02-17 15:01 ` Damien Lespiau
2015-02-17 15:10 ` Damien Lespiau [this message]
2015-02-06 14:56 ` [PATCH 5/7] drm/i915/skl: Updated the gen9_enable_rps function akash.goel
2015-02-17 15:47 ` Damien Lespiau
2015-02-18 4:59 ` Akash Goel
2015-02-06 14:56 ` [PATCH 6/7] drm/i915/skl: Updated the 'i915_frequency_info' debugs function akash.goel
2015-02-17 15:38 ` Damien Lespiau
2015-02-18 6:47 ` Akash Goel
2015-02-06 14:56 ` [PATCH 7/7] drm/i915/skl: Enabling processing of Turbo interrupts akash.goel
2015-02-06 19:40 ` shuang.he
2015-02-17 15:38 ` Damien Lespiau
2015-02-17 15:51 ` [PATCH 0/7] Added missing changes for Turbo feature on SKL Damien Lespiau
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=20150217151033.GC23520@strange.ger.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=akash.goel@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox