From: Daniel Vetter <daniel@ffwll.ch>
To: akash.goel@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Macros to convert PM time interval values to microseconds
Date: Tue, 26 Apr 2016 16:06:05 +0200 [thread overview]
Message-ID: <20160426140605.GM8291@phenom.ffwll.local> (raw)
In-Reply-To: <1461350146-23454-1-git-send-email-akash.goel@intel.com>
On Sat, Apr 23, 2016 at 12:05:44AM +0530, akash.goel@intel.com wrote:
> From: Akash Goel <akash.goel@intel.com>
>
> Added a new GT_PM_INTERVAL_TO_US macro to perform the platform
> specific conversion of PM time interval values to microseconds unit.
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Akash Goel <akash.goel@intel.com>
> ---
> drivers/gpu/drm/i915/i915_reg.h | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index 9464ba3..eacd9ae 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -2939,6 +2939,15 @@ enum skl_disp_power_wells {
> INTERVAL_1_33_US(us)) : \
> INTERVAL_1_28_US(us))
>
> +#define INTERVAL_1_28_TO_US(interval) (((interval) << 7) / 100)
> +#define INTERVAL_1_33_TO_US(interval) (((interval) << 2) / 3)
> +#define INTERVAL_0_833_TO_US(interval) (((interval) * 5) / 6)
> +#define GT_PM_INTERVAL_TO_US(dev_priv, interval) (IS_GEN9(dev_priv) ? \
> + (IS_BROXTON(dev_priv) ? \
> + INTERVAL_0_833_TO_US(interval) : \
> + INTERVAL_1_33_TO_US(interval)) : \
> + INTERVAL_1_28_TO_US(interval))
Bikeshed, but I think once we have platform logic in there a real inline
functino starts to look better.
Feel free to ignore since already pushed.
-Daniel
> +
> /*
> * Logical Context regs
> */
> --
> 1.9.2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
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-26 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 18:35 [PATCH 1/3] drm/i915: Macros to convert PM time interval values to microseconds akash.goel
2016-04-22 18:35 ` [PATCH v2 3/3] drm/i915/bxt: Explicitly clear the Turbo control register akash.goel
2016-04-22 18:35 ` [PATCH v3 2/3] drm/i915: Correct the i915_frequency_info debugfs output akash.goel
2016-04-24 9:53 ` ✗ Fi.CI.BAT: warning for series starting with [1/3] drm/i915: Macros to convert PM time interval values to microseconds Patchwork
2016-04-24 10:37 ` Chris Wilson
2016-04-26 14:06 ` Daniel Vetter [this message]
2016-04-26 14:29 ` [PATCH 1/3] " Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2016-04-21 7:37 [PATCH 1/2] drm/i915: Correct the i915_frequency_info debugfs output Goel, Akash
2016-04-22 11:52 ` [PATCH 1/3] drm/i915: Macros to convert PM time interval values to microseconds akash.goel
2016-04-22 11:58 ` Chris Wilson
2016-04-22 12:56 ` 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=20160426140605.GM8291@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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