Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/guc: Move ARAT interrupts enabling to the upload step
Date: Wed, 19 Jun 2024 16:43:04 +0000	[thread overview]
Message-ID: <ZnMKmN2A1HaQNaaN@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240619163413.817-1-michal.wajdeczko@intel.com>

On Wed, Jun 19, 2024 at 06:34:13PM +0200, Michal Wajdeczko wrote:
> Even though ARAT interrupts are enabled by default, we still want
> to keep the code that enables them. But instead doing that in the
> CTB enabling step, move this code to the upload step, where we
> already setup few other registers related to GuC.
> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>

Reviewed-by: Matthew Brost <matthew.brost@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_guc.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index 7ecb509c87d7..02c028d0e91b 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -476,6 +476,9 @@ static void guc_prepare_xfer(struct xe_guc *guc)
>  	xe_mmio_write32(gt, GUC_SHIM_CONTROL, shim_flags);
>  
>  	xe_mmio_write32(gt, GT_PM_CONFIG, GT_DOORBELL_ENABLE);
> +
> +	/* Make sure GuC receives ARAT interrupts */
> +	xe_mmio_rmw32(gt, PMINTRMSK, ARAT_EXPIRED_INTRMSK, 0);
>  }
>  
>  /*
> @@ -865,9 +868,6 @@ int xe_guc_enable_communication(struct xe_guc *guc)
>  		guc_enable_irq(guc);
>  	}
>  
> -	xe_mmio_rmw32(guc_to_gt(guc), PMINTRMSK,
> -		      ARAT_EXPIRED_INTRMSK, 0);
> -
>  	err = xe_guc_ct_enable(&guc->ct);
>  	if (err)
>  		return err;
> -- 
> 2.43.0
> 

  reply	other threads:[~2024-06-19 16:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 16:34 [PATCH] drm/xe/guc: Move ARAT interrupts enabling to the upload step Michal Wajdeczko
2024-06-19 16:43 ` Matthew Brost [this message]
2024-06-19 16:43 ` ✓ CI.Patch_applied: success for " Patchwork
2024-06-19 16:43 ` ✓ CI.checkpatch: " Patchwork
2024-06-19 16:44 ` ✓ CI.KUnit: " Patchwork
2024-06-19 16:56 ` ✓ CI.Build: " Patchwork
2024-06-19 16:58 ` ✗ CI.Hooks: failure " Patchwork
2024-06-19 17:00 ` ✓ CI.checksparse: success " Patchwork
2024-06-19 17:22 ` ✓ CI.BAT: " Patchwork
2024-06-19 22:37 ` ✗ CI.FULL: failure " Patchwork
2024-06-19 22:45   ` Michal Wajdeczko

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=ZnMKmN2A1HaQNaaN@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@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