Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> writes: > It appears that Elkhart Lake uses the same clock for CTX_TIMESTAMP as > CS_TIMESTAMP, leaving Icelake as the odd one out. I am repeating myself: weird. ...but true. > > Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/3024 > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> Reviewed-by: Mika Kuoppala <mika.kuoppala@xxxxxxxxxxxxxxx> > --- > drivers/gpu/drm/i915/gt/intel_gt_clock_utils.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/i915/gt/intel_gt_clock_utils.c b/drivers/gpu/drm/i915/gt/intel_gt_clock_utils.c > index f8c79efb1a87..09b290fe0867 100644 > --- a/drivers/gpu/drm/i915/gt/intel_gt_clock_utils.c > +++ b/drivers/gpu/drm/i915/gt/intel_gt_clock_utils.c > @@ -160,7 +160,7 @@ void intel_gt_init_clock_frequency(struct intel_gt *gt) > gt->clock_period_ns = intel_gt_clock_interval_to_ns(gt, 1); > > /* Icelake appears to use another fixed frequency for CTX_TIMESTAMP */ > - if (IS_GEN(gt->i915, 11)) > + if (IS_ICELAKE(gt->i915)) > gt->clock_period_ns = NSEC_PER_SEC / 13750000; > > GT_TRACE(gt, > -- > 2.20.1 > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/intel-gfx _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
