Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Dmitry Sepp <dmitry.sepp@opensynergy.com>
To: linux-media@vger.kernel.org
Cc: virtio-dev@lists.oasis-open.org, acourbot@chromium.org,
	alexlau@chromium.org, daniel@ffwll.ch, dgreid@chromium.org,
	dstaessens@chromium.org, egranata@google.com, fziglio@redhat.com,
	hverkuil@xs4all.nl, keiichiw@chromium.org, kraxel@redhat.com,
	marcheu@chromium.org, posciak@chromium.org,
	spice-devel@lists.freedesktop.org, stevensd@chromium.org,
	tfiga@chromium.org, uril@redhat.com,
	samiullah.khawaja@opensynergy.com, kiran.pawar@opensynergy.com
Subject: [virtio-dev] [PATCH v2 0/1] Virtio Video V4L2 driver
Date: Tue, 18 Feb 2020 21:27:52 +0100	[thread overview]
Message-ID: <20200218202753.652093-1-dmitry.sepp@opensynergy.com> (raw)

Hi all,

This is a v4l2 virtio video driver for the virtio-video device
specification v3 [1].

The first version of the driver was introduced here [2].

Changes v1 -> v2:
* support the v3 spec (mostly)
* add a module parameter to ask for pages from ZONE_DMA

What is not implemented:
* Plane layout flags should be used to propagate number of planes to
  user-space
* There is no real use of stream creation with bitstream format in the
  parameter list. The driver just uses the first bitstream format from
  the list.
* Setting bitrate is done in a different way compared to the spec. This
  is because it has been already agreed on that the way the spec
  currently describes it requires changes.

Potential improvements:
* Do not send stream_create from open. Use corresponding state machine
  condition to do this.
* Do not send stream_destroy from close. Do it in reqbufs(0).
* Cache format and control settings. Reduce calls to the device.

Best regards,
Dmitry.

[1] https://markmail.org/message/dmw3pr4fuajvarth
[2] https://markmail.org/message/wnnv6r6myvgb5at6



---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


             reply	other threads:[~2020-02-18 20:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18 20:27 Dmitry Sepp [this message]
2020-02-18 20:27 ` [virtio-dev] [PATCH v2 1/1] video_video: Add the Virtio Video V4L2 driver Dmitry Sepp
2020-03-10 10:24   ` [virtio-dev] " Keiichi Watanabe
2020-03-12 11:40     ` Dmitry Sepp
2020-03-13 11:38       ` Keiichi Watanabe
     [not found]   ` <d79df162-5fcc-6ff9-8480-4cff3548bb4a@xs4all.nl>
2020-03-12 10:15     ` Dmitry Sepp
     [not found]       ` <6f8c37b1-8dc4-e3bb-01ed-4ebedaf90915@xs4all.nl>
2020-03-12 11:48         ` Dmitry Sepp
2020-03-13 10:05           ` Tomasz Figa
2020-03-13 10:27             ` Dmitry Sepp
2020-03-13 11:11               ` Tomasz Figa
2020-03-16 10:36                 ` Dmitry Sepp
2020-03-17  6:46   ` Keiichi Watanabe
2020-03-17  6:53     ` Keiichi Watanabe
2020-03-17  9:10       ` Dmitry Sepp
2020-03-17  9:18         ` Keiichi Watanabe
     [not found] ` <c4d7622b-e396-3920-0e14-5a73a0225c0f@xs4all.nl>
2020-03-12  9:03   ` [virtio-dev] Re: [PATCH v2 0/1] " Dmitry Sepp
2020-03-12  9:49   ` Keiichi Watanabe
     [not found]     ` <1ac18708-262f-c751-d955-267931270028@xs4all.nl>
2020-03-12 10:11       ` Keiichi Watanabe
2020-03-12 10:29       ` Dmitry Sepp
     [not found]         ` <75f3a24ac5cd4f656aadf4312bdbcb70a6803a6e.camel@ndufresne.ca>
2020-03-13  7:54           ` Keiichi Watanabe
2020-03-13 10:09             ` Dmitry Sepp
2020-03-13 11:53               ` Keiichi Watanabe
2020-03-13 10:20           ` Dmitry Sepp

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=20200218202753.652093-1-dmitry.sepp@opensynergy.com \
    --to=dmitry.sepp@opensynergy.com \
    --cc=acourbot@chromium.org \
    --cc=alexlau@chromium.org \
    --cc=daniel@ffwll.ch \
    --cc=dgreid@chromium.org \
    --cc=dstaessens@chromium.org \
    --cc=egranata@google.com \
    --cc=fziglio@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=keiichiw@chromium.org \
    --cc=kiran.pawar@opensynergy.com \
    --cc=kraxel@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=marcheu@chromium.org \
    --cc=posciak@chromium.org \
    --cc=samiullah.khawaja@opensynergy.com \
    --cc=spice-devel@lists.freedesktop.org \
    --cc=stevensd@chromium.org \
    --cc=tfiga@chromium.org \
    --cc=uril@redhat.com \
    --cc=virtio-dev@lists.oasis-open.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