From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
<linux-kernel@vger.kernel.org>,
"Tomas Winkler" <tomas.winkler@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-xe] [PATCH v2 0/4] drm/xe/gsc: add initial gsc support
Date: Mon, 18 Sep 2023 12:06:42 -0400 [thread overview]
Message-ID: <ZQh1klXZSf9/qqf5@intel.com> (raw)
In-Reply-To: <20230914080138.4178295-1-alexander.usyskin@intel.com>
On Thu, Sep 14, 2023 at 11:01:34AM +0300, Alexander Usyskin wrote:
> Add initial GSC support for DG1 and DG2.
> Create mei-gscfi auxiliary device and add
> support for device created by Xe to the mei-gsc driver.
why are we not adding the GSC already? because dependency on the GSC
engine or something like that?
>
> This series intended to be merged intto Xe tree,
> the only patch that touches char-misc is addition
> of id and alias in mei-gsc.
>
> V2: Added heci_ to struct and APIs
> heci_gsc moved under xe_device as GSC is not under GT
>
> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
>
> Vitaly Lubart (4):
> drm/xe/gsc: add HECI2 register offsets
> drm/xe/gsc: add has_heci_gscfi indication to device
> drm/xe/gsc: add gsc device support
> mei: gsc: add support for auxiliary device created by Xe driver
>
> drivers/gpu/drm/xe/Kconfig | 1 +
> drivers/gpu/drm/xe/Makefile | 1 +
> drivers/gpu/drm/xe/regs/xe_regs.h | 4 +
> drivers/gpu/drm/xe/xe_device.c | 4 +
> drivers/gpu/drm/xe/xe_device_types.h | 7 +
> drivers/gpu/drm/xe/xe_heci_gsc.c | 205 +++++++++++++++++++++++++++
> drivers/gpu/drm/xe/xe_heci_gsc.h | 35 +++++
> drivers/gpu/drm/xe/xe_irq.c | 14 +-
> drivers/gpu/drm/xe/xe_pci.c | 9 +-
> drivers/misc/mei/gsc-me.c | 5 +
> 10 files changed, 281 insertions(+), 4 deletions(-)
> create mode 100644 drivers/gpu/drm/xe/xe_heci_gsc.c
> create mode 100644 drivers/gpu/drm/xe/xe_heci_gsc.h
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-09-18 16:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 8:01 [PATCH v2 0/4] drm/xe/gsc: add initial gsc support Alexander Usyskin
2023-09-14 8:01 ` [PATCH v2 1/4] drm/xe/gsc: add HECI2 register offsets Alexander Usyskin
2023-09-18 16:07 ` [Intel-xe] " Rodrigo Vivi
2023-09-14 8:01 ` [PATCH v2 2/4] drm/xe/gsc: add has_heci_gscfi indication to device Alexander Usyskin
2023-09-18 16:09 ` [Intel-xe] " Rodrigo Vivi
2023-09-14 8:01 ` [PATCH v2 3/4] drm/xe/gsc: add gsc device support Alexander Usyskin
2023-09-18 16:25 ` [Intel-xe] " Rodrigo Vivi
2023-09-19 14:51 ` Usyskin, Alexander
2023-09-20 8:59 ` Usyskin, Alexander
2023-09-14 8:01 ` [PATCH v2 4/4] mei: gsc: add support for auxiliary device created by Xe driver Alexander Usyskin
2023-09-18 16:26 ` [Intel-xe] " Rodrigo Vivi
2023-09-18 16:06 ` Rodrigo Vivi [this message]
2023-09-20 6:15 ` [Intel-xe] [PATCH v2 0/4] drm/xe/gsc: add initial gsc support Usyskin, Alexander
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=ZQh1klXZSf9/qqf5@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=tomas.winkler@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