From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Aravind Iddamsetty <aravind.iddamsetty@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v3 1/2] drm/xe: Get GT clock to nanosecs
Date: Tue, 08 Aug 2023 22:08:08 -0700 [thread overview]
Message-ID: <878rakyf9j.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230808115436.400611-2-aravind.iddamsetty@intel.com>
On Tue, 08 Aug 2023 04:54:35 -0700, Aravind Iddamsetty wrote:
>
> Helpers to get GT clock to nanosecs
Helper to convert GT clock cycles to nanoseconds.
> v2: Use DIV_ROUND_CLOSEST_ULL helper(Ashutosh)
>
> Reviewed-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
> Signed-off-by: Aravind Iddamsetty <aravind.iddamsetty@intel.com>
> ---
> drivers/gpu/drm/xe/xe_gt_clock.c | 5 +++++
> drivers/gpu/drm/xe/xe_gt_clock.h | 4 +++-
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_clock.c b/drivers/gpu/drm/xe/xe_gt_clock.c
> index 2f77b8bbcf53..88c29ad84146 100644
> --- a/drivers/gpu/drm/xe/xe_gt_clock.c
> +++ b/drivers/gpu/drm/xe/xe_gt_clock.c
> @@ -78,3 +78,8 @@ int xe_gt_clock_init(struct xe_gt *gt)
> gt->info.clock_freq = freq;
> return 0;
> }
> +
> +u64 xe_gt_clock_interval_to_ns(const struct xe_gt *gt, u64 count)
I know this name is used in i915 but my 2 cents on this is that a better
name is 'xe_gt_clock_cycles_to_ns', since count is the number of clock
cycles. So optional but you may consider this name.
> +{
> + return DIV_ROUND_CLOSEST_ULL(count * NSEC_PER_SEC, gt->info.clock_freq);
> +}
> diff --git a/drivers/gpu/drm/xe/xe_gt_clock.h b/drivers/gpu/drm/xe/xe_gt_clock.h
> index 511923afd224..91fc9b7e83f5 100644
> --- a/drivers/gpu/drm/xe/xe_gt_clock.h
> +++ b/drivers/gpu/drm/xe/xe_gt_clock.h
> @@ -6,8 +6,10 @@
> #ifndef _XE_GT_CLOCK_H_
> #define _XE_GT_CLOCK_H_
>
> +#include <linux/types.h>
This is for HDRTEST I guess?
> +
> struct xe_gt;
>
> int xe_gt_clock_init(struct xe_gt *gt);
> -
> +u64 xe_gt_clock_interval_to_ns(const struct xe_gt *gt, u64 count);
> #endif
> --
> 2.25.1
>
Also not sure if this merits a patch on its own so can be merged into the
giant PMU patch if you wish.
In any case, with the optional tweaks above, this is:
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
next prev parent reply other threads:[~2023-08-09 5:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 11:54 [Intel-xe] [PATCH v3 0/2] drm/xe/pmu: Enable PMU interface Aravind Iddamsetty
2023-08-08 11:54 ` [Intel-xe] [PATCH v3 1/2] drm/xe: Get GT clock to nanosecs Aravind Iddamsetty
2023-08-09 5:08 ` Dixit, Ashutosh [this message]
2023-08-09 11:07 ` Iddamsetty, Aravind
2023-08-08 11:54 ` [Intel-xe] [PATCH v3 2/2] drm/xe/pmu: Enable PMU interface Aravind Iddamsetty
2023-08-09 7:28 ` Dixit, Ashutosh
2023-08-09 7:46 ` Iddamsetty, Aravind
2023-08-09 11:39 ` Iddamsetty, Aravind
2023-08-10 2:17 ` Dixit, Ashutosh
2023-08-10 2:06 ` Dixit, Ashutosh
2023-08-09 9:55 ` Iddamsetty, Aravind
2023-08-09 11:57 ` Iddamsetty, Aravind
2023-08-09 13:11 ` Iddamsetty, Aravind
2023-08-10 2:40 ` Dixit, Ashutosh
2023-08-10 8:10 ` Iddamsetty, Aravind
2023-08-10 21:55 ` Rodrigo Vivi
2023-08-11 3:38 ` Dixit, Ashutosh
2023-08-11 6:17 ` Iddamsetty, Aravind
2023-08-11 19:17 ` Dixit, Ashutosh
2023-08-14 2:02 ` Dixit, Ashutosh
2023-08-14 4:19 ` Iddamsetty, Aravind
2023-08-08 12:08 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe/pmu: Enable PMU interface (rev3) Patchwork
2023-08-08 12:09 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-08 12:10 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-08 12:14 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-08 12:14 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-08 12:14 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-08 12:51 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 13:12 [Intel-xe] [PATCH v4 0/2] drm/xe/pmu: Enable PMU interface Aravind Iddamsetty
2023-08-14 13:12 ` [Intel-xe] [PATCH v3 1/2] drm/xe: Get GT clock to nanosecs Aravind Iddamsetty
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=878rakyf9j.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=aravind.iddamsetty@intel.com \
--cc=intel-xe@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