From: Thomas Zimmermann <tzimmermann@suse.de>
To: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
dri-devel@lists.freedesktop.org, airlied@gmail.com,
daniel@ffwll.ch
Cc: andrzej.kacprowski@linux.intel.com, stanislaw.gruszka@linux.intel.com
Subject: Re: [PATCH v3 RESEND 0/7] New DRM driver for Intel VPU
Date: Tue, 1 Nov 2022 09:58:08 +0100 [thread overview]
Message-ID: <49050012-a53b-98bb-16ec-bc84000cf969@suse.de> (raw)
In-Reply-To: <20220924151149.323622-1-jacek.lawrynowicz@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 5620 bytes --]
Hi
Am 24.09.22 um 17:11 schrieb Jacek Lawrynowicz:
> Hi,
>
> This patchset contains a new Linux* Kernel Driver for Intel® VPUs.
>
> VPU stands for Versatile Processing Unit and it is an AI inference accelerator
> integrated with Intel non-server CPUs starting from 14th generation.
> VPU enables efficient execution of Deep Learning applications
> like object detection, classification etc.
>
> Driver is part of gpu/drm subsystem because VPU is similar in operation to
> an integrated GPU. Reusing drm driver init, ioctl handling, gem and prime
> helpers and drm_mm allows to minimize code duplication in the kernel.
>
> The whole driver is licensed under GPL-2.0-only except for two headers imported
> from the firmware that are MIT licensed.
>
> User mode driver stack consists of Level Zero API driver and OpenVINO plugin.
> Both should be open-sourced by the end of Q4.
> The firmware for the VPU will be distributed as a closed source binary.
>
> I'm resending v3 patchset with correct Dave's email.
>
> Regards,
> Jacek
>
> v3:
> - Fixed alignment warning in ivpu_ipc.c when building with W=1
>
> v2: https://lore.kernel.org/all/20220913121017.993825-1-jacek.lawrynowicz@linux.intel.com/
> - Rename the driver from "drm/vpu" to "drm/ivpu"
> - Add a TODO file
> - Add support for WC buffers
>
> v1: https://lore.kernel.org/all/20220728131709.1087188-1-jacek.lawrynowicz@linux.intel.com/
>
> Jacek Lawrynowicz (7):
> drm/ivpu: Introduce a new DRM driver for Intel VPU
> drm/ivpu: Add Intel VPU MMU support
> drm/ivpu: Add GEM buffer object management
> drm/ivpu: Add IPC driver and JSM messages
> drm/ivpu: Implement firmware parsing and booting
> drm/ivpu: Add command buffer submission logic
> drm/ivpu: Add PM support
>
> MAINTAINERS | 8 +
> drivers/gpu/drm/Kconfig | 2 +
> drivers/gpu/drm/Makefile | 1 +
> drivers/gpu/drm/ivpu/Kconfig | 12 +
> drivers/gpu/drm/ivpu/Makefile | 16 +
> drivers/gpu/drm/ivpu/TODO | 7 +
> drivers/gpu/drm/ivpu/ivpu_drv.c | 643 ++++++++++++++
> drivers/gpu/drm/ivpu/ivpu_drv.h | 178 ++++
> drivers/gpu/drm/ivpu/ivpu_fw.c | 426 +++++++++
> drivers/gpu/drm/ivpu/ivpu_fw.h | 38 +
> drivers/gpu/drm/ivpu/ivpu_gem.c | 836 ++++++++++++++++++
> drivers/gpu/drm/ivpu/ivpu_gem.h | 128 +++
> drivers/gpu/drm/ivpu/ivpu_hw.h | 169 ++++
> drivers/gpu/drm/ivpu/ivpu_hw_mtl.c | 1060 +++++++++++++++++++++++
> drivers/gpu/drm/ivpu/ivpu_hw_mtl_reg.h | 468 ++++++++++
> drivers/gpu/drm/ivpu/ivpu_hw_reg_io.h | 115 +++
> drivers/gpu/drm/ivpu/ivpu_ipc.c | 508 +++++++++++
> drivers/gpu/drm/ivpu/ivpu_ipc.h | 90 ++
> drivers/gpu/drm/ivpu/ivpu_job.c | 629 ++++++++++++++
> drivers/gpu/drm/ivpu/ivpu_job.h | 73 ++
> drivers/gpu/drm/ivpu/ivpu_jsm_msg.c | 220 +++++
> drivers/gpu/drm/ivpu/ivpu_jsm_msg.h | 25 +
> drivers/gpu/drm/ivpu/ivpu_mmu.c | 888 +++++++++++++++++++
> drivers/gpu/drm/ivpu/ivpu_mmu.h | 53 ++
> drivers/gpu/drm/ivpu/ivpu_mmu_context.c | 419 +++++++++
> drivers/gpu/drm/ivpu/ivpu_mmu_context.h | 49 ++
> drivers/gpu/drm/ivpu/ivpu_pm.c | 352 ++++++++
> drivers/gpu/drm/ivpu/ivpu_pm.h | 38 +
> drivers/gpu/drm/ivpu/vpu_boot_api.h | 241 ++++++
> drivers/gpu/drm/ivpu/vpu_jsm_api.h | 616 +++++++++++++
> include/uapi/drm/ivpu_drm.h | 343 ++++++++
You have to add yourself to MAINTAINERS.
I assume that there's a FOSS userspace available?
Best regards
Thomas
> 31 files changed, 8651 insertions(+)
> create mode 100644 drivers/gpu/drm/ivpu/Kconfig
> create mode 100644 drivers/gpu/drm/ivpu/Makefile
> create mode 100644 drivers/gpu/drm/ivpu/TODO
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_drv.c
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_drv.h
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_fw.c
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_fw.h
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_gem.c
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_gem.h
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_hw.h
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_hw_mtl.c
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_hw_mtl_reg.h
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_hw_reg_io.h
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_ipc.c
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_ipc.h
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_job.c
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_job.h
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_jsm_msg.c
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_jsm_msg.h
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_mmu.c
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_mmu.h
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_mmu_context.c
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_mmu_context.h
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_pm.c
> create mode 100644 drivers/gpu/drm/ivpu/ivpu_pm.h
> create mode 100644 drivers/gpu/drm/ivpu/vpu_boot_api.h
> create mode 100644 drivers/gpu/drm/ivpu/vpu_jsm_api.h
> create mode 100644 include/uapi/drm/ivpu_drm.h
>
> --
> 2.34.1
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-11-01 8:58 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 15:11 [PATCH v3 RESEND 0/7] New DRM driver for Intel VPU Jacek Lawrynowicz
2022-09-24 15:11 ` [PATCH v3 1/7] drm/ivpu: Introduce a new " Jacek Lawrynowicz
2022-10-24 23:00 ` Jeffrey Hugo
2022-10-25 11:42 ` Jacek Lawrynowicz
2022-10-25 11:57 ` Thomas Zimmermann
2022-10-26 12:07 ` Jacek Lawrynowicz
2022-10-26 12:21 ` Thomas Zimmermann
2022-10-25 14:08 ` Jeffrey Hugo
2022-10-26 12:21 ` Jacek Lawrynowicz
2022-10-25 12:38 ` Thomas Zimmermann
2022-10-28 16:00 ` Jacek Lawrynowicz
2022-09-24 15:11 ` [PATCH v3 2/7] drm/ivpu: Add Intel VPU MMU support Jacek Lawrynowicz
2022-10-26 0:12 ` Jeffrey Hugo
2022-10-27 9:14 ` Jacek Lawrynowicz
2022-10-27 17:44 ` Jeffrey Hugo
2022-11-17 14:00 ` Jacek Lawrynowicz
2022-11-01 8:56 ` Thomas Zimmermann
2022-11-18 10:18 ` Jacek Lawrynowicz
2022-11-01 9:00 ` Thomas Zimmermann
2022-11-18 10:15 ` Jacek Lawrynowicz
2022-09-24 15:11 ` [PATCH v3 3/7] drm/ivpu: Add GEM buffer object management Jacek Lawrynowicz
2022-10-25 12:41 ` Thomas Zimmermann
2022-10-26 11:26 ` Jacek Lawrynowicz
2022-10-26 12:06 ` Thomas Zimmermann
2022-09-24 15:11 ` [PATCH v3 4/7] drm/ivpu: Add IPC driver and JSM messages Jacek Lawrynowicz
2022-11-01 10:02 ` Thomas Zimmermann
2022-12-07 9:47 ` Jacek Lawrynowicz
2022-09-24 15:11 ` [PATCH v3 5/7] drm/ivpu: Implement firmware parsing and booting Jacek Lawrynowicz
2022-11-01 10:08 ` Thomas Zimmermann
2022-11-14 8:21 ` Jacek Lawrynowicz
2022-09-24 15:11 ` [PATCH v3 6/7] drm/ivpu: Add command buffer submission logic Jacek Lawrynowicz
2022-09-24 15:11 ` [PATCH v3 7/7] drm/ivpu: Add PM support Jacek Lawrynowicz
2022-11-01 8:58 ` Thomas Zimmermann [this message]
2022-11-01 10:17 ` [PATCH v3 RESEND 0/7] New DRM driver for Intel VPU Thomas Zimmermann
2022-12-07 9:50 ` Jacek Lawrynowicz
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=49050012-a53b-98bb-16ec-bc84000cf969@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=andrzej.kacprowski@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=stanislaw.gruszka@linux.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;
as well as URLs for NNTP newsgroup(s).