From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH v2 2/2] drm/xe/gsc: add support for GSC proxy interrupt
Date: Thu, 11 Jan 2024 20:02:55 +0000 [thread overview]
Message-ID: <36c5bc13c191f34cfa6b091f8f4b73d855fed02c.camel@intel.com> (raw)
In-Reply-To: <20240110004416.1127942-3-daniele.ceraolospurio@intel.com>
On Tue, 2024-01-09 at 16:44 -0800, Daniele Ceraolo Spurio wrote:
> The GSC notifies us of a proxy request via the HECI2 interrupt. The
> interrupt must be enabled both in the HECI layer and in our usual gt irq
> programming; for the latter, the interrupt is enabled via the same enable
> register as the GSC CS, but it does have its own mask register. When the
alan:snip
LGTM: Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>
next prev parent reply other threads:[~2024-01-11 20:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 0:44 [PATCH v2 0/2] drm/xe: GSC proxy support Daniele Ceraolo Spurio
2024-01-10 0:44 ` [PATCH v2 1/2] drm/xe/gsc: Initialize GSC proxy Daniele Ceraolo Spurio
2024-01-11 20:02 ` Teres Alexis, Alan Previn
2024-01-16 6:13 ` Kandpal, Suraj
2024-01-16 16:53 ` Daniele Ceraolo Spurio
2024-01-10 0:44 ` [PATCH v2 2/2] drm/xe/gsc: add support for GSC proxy interrupt Daniele Ceraolo Spurio
2024-01-11 20:02 ` Teres Alexis, Alan Previn [this message]
2024-01-10 2:38 ` ✓ CI.Patch_applied: success for drm/xe: GSC proxy support (rev2) Patchwork
2024-01-10 2:38 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-10 2:39 ` ✓ CI.KUnit: success " Patchwork
2024-01-10 2:47 ` ✓ CI.Build: " Patchwork
2024-01-10 2:47 ` ✗ CI.Hooks: failure " Patchwork
2024-01-10 2:48 ` ✓ CI.checksparse: success " Patchwork
2024-01-10 3:26 ` ✗ CI.BAT: failure " Patchwork
2024-01-17 0:40 ` ✓ CI.Patch_applied: success for drm/xe: GSC proxy support (rev3) Patchwork
2024-01-17 0:41 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-17 0:42 ` ✓ CI.KUnit: success " Patchwork
2024-01-17 0:49 ` ✓ CI.Build: " Patchwork
2024-01-17 0:49 ` ✗ CI.Hooks: failure " Patchwork
2024-01-17 0:51 ` ✓ CI.checksparse: success " Patchwork
2024-01-17 16:39 ` ✓ CI.Patch_applied: " Patchwork
2024-01-17 16:39 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-17 16:40 ` ✓ CI.KUnit: success " Patchwork
2024-01-17 16:47 ` ✓ CI.Build: " Patchwork
2024-01-17 16:48 ` ✗ CI.Hooks: failure " Patchwork
2024-01-17 16:49 ` ✓ CI.checksparse: success " Patchwork
2024-01-17 17:12 ` ✓ CI.BAT: " 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=36c5bc13c191f34cfa6b091f8f4b73d855fed02c.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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