From: Sam Ravnborg <sam@ravnborg.org>
To: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
Cc: Dave Airlie <airlied@linux.ie>,
dri-devel <dri-devel@lists.freedesktop.org>,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
andrzej.kacprowski@linux.intel.com, "Koenig,
Christian" <Christian.Koenig@amd.com>
Subject: Re: [PATCH v1 0/7] New DRM driver for Intel VPU
Date: Mon, 8 Aug 2022 20:53:54 +0200 [thread overview]
Message-ID: <YvFbwqOKwwLPoGKi@ravnborg.org> (raw)
In-Reply-To: <20220808144918.GA2666787@linux.intel.com>
Hi Stanislaw,
> I'm not sure what we can add to TODO file, from driver perspective
> I think it's pretty much ready for merging (except renaming), just
> other components: F/W and user-space are not yet released.
>
> > I think I'd like Christian/Maarten to maybe review the fencing/uapi,
> > to make sure nothing too much is wrong there. The submit/waitbo model
> > is getting a bit old, and using syncobjs might be useful to make it
> > more modern. Is this device meant to be used by multiple users at
> > once? Maybe we'd want scheduler integration for it as well (which I
> > think I saw mentioned somewhere in passing).
>
> In the future we are planning to add support for
> HW based scheduling (we are also looking at SW scheduler) and we will
> likely revisit submit/sync APIs at that time.
This is already two entries in the TODO file.
Sam
prev parent reply other threads:[~2022-08-08 18:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 13:17 [PATCH v1 0/7] New DRM driver for Intel VPU Jacek Lawrynowicz
2022-07-28 13:17 ` [PATCH v1 1/7] drm/vpu: Introduce a new " Jacek Lawrynowicz
2022-07-28 13:17 ` [PATCH v1 2/7] drm/vpu: Add Intel VPU MMU support Jacek Lawrynowicz
2022-07-28 13:17 ` [PATCH v1 3/7] drm/vpu: Add GEM buffer object management Jacek Lawrynowicz
2022-07-28 13:17 ` [PATCH v1 4/7] drm/vpu: Add IPC driver and JSM messages Jacek Lawrynowicz
2022-07-28 13:17 ` [PATCH v1 5/7] drm/vpu: Implement firmware parsing and booting Jacek Lawrynowicz
2022-07-28 13:17 ` [PATCH v1 6/7] drm/vpu: Add command buffer submission logic Jacek Lawrynowicz
2022-07-28 13:17 ` [PATCH v1 7/7] drm/vpu: Add PM support Jacek Lawrynowicz
2022-08-08 2:34 ` [PATCH v1 0/7] New DRM driver for Intel VPU Dave Airlie
2022-08-08 14:49 ` Stanislaw Gruszka
2022-08-08 18:53 ` Sam Ravnborg [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=YvFbwqOKwwLPoGKi@ravnborg.org \
--to=sam@ravnborg.org \
--cc=Christian.Koenig@amd.com \
--cc=airlied@linux.ie \
--cc=andrzej.kacprowski@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.