From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>
Cc: saurabhg.gupta@intel.com, lucas.demarchi@intel.com,
intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe: clear the serviced bits on INTR_IDENTITY_REG
Date: Fri, 3 Nov 2023 14:58:53 -0400 [thread overview]
Message-ID: <ZUVC7Vb8UEo7+6i5@intel.com> (raw)
In-Reply-To: <20231103182922.909972-1-jonathan.cavitt@intel.com>
On Fri, Nov 03, 2023 at 11:29:22AM -0700, Jonathan Cavitt wrote:
> On XE, we have to write the serviced bits to the
> INTR_IDENTITY_REG. Do so.
Please have a more descriptive commit message, explaining why
do we need or what are you trying to solve.
like, why does Xe needs but i915 can stay with the other code?
what bug, condition or corner case are you attempting to address?
>
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> CC: Daniele Spurio Ceraolo <daniele.ceraolospurio@intel.com>
> CC: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_irq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_irq.c b/drivers/gpu/drm/xe/xe_irq.c
> index 21d5273d7e611..c5315e02fc5bb 100644
> --- a/drivers/gpu/drm/xe/xe_irq.c
> +++ b/drivers/gpu/drm/xe/xe_irq.c
> @@ -232,7 +232,7 @@ gt_engine_identity(struct xe_device *xe,
> return 0;
> }
>
> - xe_mmio_write32(mmio, INTR_IDENTITY_REG(bank), INTR_DATA_VALID);
> + xe_mmio_write32(mmio, INTR_IDENTITY_REG(bank), ident);
>
> return ident;
> }
> --
> 2.25.1
>
prev parent reply other threads:[~2023-11-03 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 18:29 [Intel-xe] [PATCH] drm/xe: clear the serviced bits on INTR_IDENTITY_REG Jonathan Cavitt
2023-11-03 18:58 ` Rodrigo Vivi [this message]
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=ZUVC7Vb8UEo7+6i5@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=saurabhg.gupta@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