Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-xe@lists.freedesktop.org
Cc: Jakub Kolakowski <jakub1.kolakowski@intel.com>
Subject: Re: [PATCH 2/2] drm/xe/sriov: Drop TIMESTAMP_OVERRIDE from Xe2 runtime regs
Date: Fri, 13 Sep 2024 15:40:53 +0200	[thread overview]
Message-ID: <29286880-69f4-41da-810c-e16339ca7ea2@intel.com> (raw)
In-Reply-To: <20240912215559.4070443-4-matthew.d.roper@intel.com>



On 12.09.2024 23:56, Matt Roper wrote:
> TIMESTAMP_OVERRIDE is never used to initialize the GT clock frequency on
> Xe2 platforms (and the register itself no longer exists on LNL) so drop
> it from the list of runtime registers.
> 
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Jakub Kolakowski <jakub1.kolakowski@intel.com>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c b/drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c
> index 924e75b94aec..a5bd577227d4 100644
> --- a/drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c
> +++ b/drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c
> @@ -173,7 +173,6 @@ static const struct xe_reg ver_2000_runtime_regs[] = {
>  	XE2_GT_GEOMETRY_DSS_2,		/* _MMIO(0x9154) */
>  	CTC_MODE,			/* _MMIO(0xa26c) */
>  	HUC_KERNEL_LOAD_INFO,		/* _MMIO(0xc1dc) */
> -	TIMESTAMP_OVERRIDE,		/* _MMIO(0x44074) */
>  };
>  
>  static const struct xe_reg *pick_runtime_regs(struct xe_device *xe, unsigned int *count)

Acked-by: Michal Wajdeczko <michal.wajdeczko@intel.com>

  reply	other threads:[~2024-09-13 13:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 21:56 [PATCH 1/2] drm/xe: Don't try to derive GT clock freq from display register on Xe2 Matt Roper
2024-09-12 21:56 ` [PATCH 2/2] drm/xe/sriov: Drop TIMESTAMP_OVERRIDE from Xe2 runtime regs Matt Roper
2024-09-13 13:40   ` Michal Wajdeczko [this message]
2024-09-12 22:30 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe: Don't try to derive GT clock freq from display register on Xe2 Patchwork
2024-09-12 22:30 ` ✓ CI.checkpatch: " Patchwork
2024-09-12 22:31 ` ✓ CI.KUnit: " Patchwork
2024-09-12 22:43 ` ✓ CI.Build: " Patchwork
2024-09-12 22:45 ` ✓ CI.Hooks: " Patchwork
2024-09-12 22:47 ` ✓ CI.checksparse: " Patchwork
2024-09-12 23:02 ` ✓ CI.BAT: " Patchwork
2024-09-13 14:36 ` [PATCH 1/2] " Lucas De Marchi
2024-09-13 15:25 ` ✗ CI.FULL: failure for series starting with [1/2] " Patchwork

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=29286880-69f4-41da-810c-e16339ca7ea2@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jakub1.kolakowski@intel.com \
    --cc=matthew.d.roper@intel.com \
    /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