From: Keiichi Watanabe <keiichiw@chromium.org>
To: virtio-dev@lists.oasis-open.org, linux-media@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
"Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
Dmitry Sepp <dmitry.sepp@opensynergy.com>,
Kiran Pawar <Kiran.Pawar@opensynergy.com>,
Samiullah Khawaja <samiullah.khawaja@opensynergy.com>,
Keiichi Watanabe <keiichiw@chromium.org>,
Nikolay Martyanov <Nikolay.Martyanov@opensynergy.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
acourbot@chromium.org, alexlau@chromium.org, egranata@google.com,
hverkuil@xs4all.nl, kraxel@redhat.com, posciak@chromium.org,
stevensd@chromium.org, tfiga@chromium.org
Subject: [PATCH RFC 0/1] Support virtio objects in virtio-video driver
Date: Wed, 25 Mar 2020 19:40:38 +0900 [thread overview]
Message-ID: <20200325104039.196058-1-keiichiw@chromium.org> (raw)
This implements a feature in virtio-video driver to use exported virtio
objects as video buffers. So, the users will be able to use resources
allocated by other virtio devices such as virtio-gpu.
The virtio protocol for this feature is proposed by [1].
This commit depends on the following unmerged patches:
* Virtio-video driver patch [2]
* Patch series for virtio cross-device resources [3]
* ChromeOS's local patch to use data_offset for offset of multiplanar
format [4]
[1]: https://markmail.org/message/wxdne5re7aaugbjg
[2]: https://patchwork.linuxtv.org/patch/61717/
[3]: https://patchwork.kernel.org/project/linux-media/list/?series=254707
[4]: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/1057eb620ccd3da4632c14df269d545cb9a1ccb2
Keiichi Watanabe (1):
drivers: media: virtio: Support virtio objects in virtio-video driver
drivers/media/virtio/virtio_video.h | 26 +++-
drivers/media/virtio/virtio_video_dec.c | 1 +
drivers/media/virtio/virtio_video_device.c | 131 ++++++++++++++++++++-
drivers/media/virtio/virtio_video_driver.c | 25 +++-
drivers/media/virtio/virtio_video_vq.c | 81 ++++++++++---
include/uapi/linux/virtio_video.h | 15 ++-
6 files changed, 243 insertions(+), 36 deletions(-)
--
2.25.1.696.g5e7596f4ac-goog
next reply other threads:[~2020-03-25 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 10:40 Keiichi Watanabe [this message]
2020-03-25 10:40 ` [PATCH RFC 1/1] drivers: media: virtio: Support virtio objects in virtio-video driver Keiichi Watanabe
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=20200325104039.196058-1-keiichiw@chromium.org \
--to=keiichiw@chromium.org \
--cc=Kiran.Pawar@opensynergy.com \
--cc=Nikolay.Martyanov@opensynergy.com \
--cc=acourbot@chromium.org \
--cc=alexlau@chromium.org \
--cc=dmitry.sepp@opensynergy.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=egranata@google.com \
--cc=hverkuil@xs4all.nl \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mst@redhat.com \
--cc=posciak@chromium.org \
--cc=samiullah.khawaja@opensynergy.com \
--cc=stevensd@chromium.org \
--cc=sumit.semwal@linaro.org \
--cc=tfiga@chromium.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).