From: Matthew Brost <matthew.brost@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Vinay Belgaumkar <vinay.belgaumkar@intel.com>,
John Harrison <John.C.Harrison@intel.com>
Subject: Re: [PATCH] drm/xe/guc: Drop redundant ARAT timer enabling
Date: Tue, 4 Jun 2024 00:43:39 +0000 [thread overview]
Message-ID: <Zl5jO5P4M4/0ckga@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240603190747.1372-1-michal.wajdeczko@intel.com>
On Mon, Jun 03, 2024 at 09:07:47PM +0200, Michal Wajdeczko wrote:
> This interrupt is enabled by default and there is no need to
> re-enable it as there is no other code in the Xe driver that
> could change this setting.
>
I agree this is likely the wrong location but also think it is little
unsafe to rely on default values. I recall having to add this in in i915
at one point and without this GuC submission doesn't work. How about
moving it to the IRQ layer plus a comment along the lines of should be
enabled by default but let's be paranoid and set it anyways?
Matt
> Bspec: 52572
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index 086a048876ba..f4d728350694 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -862,9 +862,6 @@ int xe_guc_enable_communication(struct xe_guc *guc)
> return err;
> }
>
> - 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
>
next prev parent reply other threads:[~2024-06-04 0:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 19:07 [PATCH] drm/xe/guc: Drop redundant ARAT timer enabling Michal Wajdeczko
2024-06-04 0:43 ` Matthew Brost [this message]
2024-06-04 12:03 ` Michal Wajdeczko
2024-06-04 21:13 ` ✓ CI.Patch_applied: success for " Patchwork
2024-06-04 21:13 ` ✓ CI.checkpatch: " Patchwork
2024-06-04 21:14 ` ✓ CI.KUnit: " Patchwork
2024-06-04 21:26 ` ✓ CI.Build: " Patchwork
2024-06-04 21:26 ` ✗ CI.Hooks: failure " Patchwork
2024-06-04 21:27 ` ✓ CI.checksparse: success " Patchwork
2024-06-04 21:55 ` ✓ CI.BAT: " Patchwork
2024-06-05 4:44 ` ✗ CI.FULL: failure " 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=Zl5jO5P4M4/0ckga@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=John.C.Harrison@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
--cc=vinay.belgaumkar@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