From: Alexander Usyskin <alexander.usyskin@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: linux-kernel@vger.kernel.org,
Tomas Winkler <tomas.winkler@intel.com>,
Alexander Usyskin <alexander.usyskin@intel.com>,
intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH v4 0/4] drm/xe/gsc: add initial gsc support
Date: Wed, 20 Sep 2023 12:41:47 +0300 [thread overview]
Message-ID: <20230920094151.1593505-1-alexander.usyskin@intel.com> (raw)
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.
This series intended to be merged into Xe tree,
the only patch that touches char-misc is addition
of id and alias in mei-gsc.
V4: no-change rebase over updated drm-xe-next to fix FTBFS
V3: Review comments addressed:
- xe_heci_gsc_init mover earlier
- part of init flow moved to dedicated functions
- KDoc fix
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 | 222 +++++++++++++++++++++++++++
drivers/gpu/drm/xe/xe_heci_gsc.h | 35 +++++
drivers/gpu/drm/xe/xe_irq.c | 21 ++-
drivers/gpu/drm/xe/xe_pci.c | 9 +-
drivers/misc/mei/gsc-me.c | 5 +
10 files changed, 302 insertions(+), 7 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 reply other threads:[~2023-09-20 9:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 9:41 Alexander Usyskin [this message]
2023-09-20 9:41 ` [Intel-xe] [PATCH v4 1/4] drm/xe/gsc: add HECI2 register offsets Alexander Usyskin
2023-09-20 9:41 ` [Intel-xe] [PATCH v4 2/4] drm/xe/gsc: add has_heci_gscfi indication to device Alexander Usyskin
2023-09-20 9:41 ` [Intel-xe] [PATCH v4 3/4] drm/xe/gsc: add gsc device support Alexander Usyskin
2023-09-20 19:58 ` Rodrigo Vivi
2023-09-20 9:41 ` [Intel-xe] [PATCH v4 4/4] mei: gsc: add support for auxiliary device created by Xe driver Alexander Usyskin
2023-09-20 9:48 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe/gsc: add initial gsc support (rev4) Patchwork
2023-09-20 9:48 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-20 9:49 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-20 9:56 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-20 9:57 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-20 9:58 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-20 10:29 ` [Intel-xe] ✓ 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=20230920094151.1593505-1-alexander.usyskin@intel.com \
--to=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=rodrigo.vivi@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