From: Dmitry Sepp <dmitry.sepp@opensynergy.com>
To: <linux-media@vger.kernel.org>, Hans Verkuil <hverkuil@xs4all.nl>
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>, <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: Re: [PATCH v2 0/1] Virtio Video V4L2 driver
Date: Thu, 12 Mar 2020 10:03:58 +0100 [thread overview]
Message-ID: <3182728.aeNJFYEL58@os-lin-dmo> (raw)
In-Reply-To: <c4d7622b-e396-3920-0e14-5a73a0225c0f@xs4all.nl>
Hi Hans,
Thanks for reviewing.
Sure, we understand the driver must pass v4l2-compliance. But the spec is not
finalized yet, so it was a bit out of the scope.
Best regards,
Dmitry.
On Mittwoch, 11. März 2020 14:26:46 CET Hans Verkuil wrote:
> Hi Dmitry,
>
> On 2/18/20 9:27 PM, Dmitry Sepp wrote:
> > 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.
>
> Some general notes:
>
> Before this can be merged it needs to pass v4l2-compliance.
>
> I also strongly recommend adding support for V4L2_PIX_FMT_FWHT to
> allow testing with the vicodec emulation driver. This will also
> allow testing all sorts of corner cases without requiring special
> hardware.
>
> Regards,
>
> Hans
>
> > Best regards,
> > Dmitry.
> >
> > [1] https://markmail.org/message/dmw3pr4fuajvarth
> > [2] https://markmail.org/message/wnnv6r6myvgb5at6
next prev parent reply other threads:[~2020-03-12 9:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 20:27 [PATCH v2 0/1] Virtio Video V4L2 driver Dmitry Sepp
2020-02-18 20:27 ` [PATCH v2 1/1] video_video: Add the " Dmitry Sepp
2020-03-10 10:24 ` Keiichi Watanabe
2020-03-11 0:09 ` Nicolas Dufresne
2020-03-12 11:40 ` Dmitry Sepp
2020-03-13 11:38 ` Keiichi Watanabe
2020-03-11 13:23 ` Hans Verkuil
2020-03-12 10:15 ` Dmitry Sepp
2020-03-12 10:18 ` Hans Verkuil
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
2020-03-11 13:26 ` [PATCH v2 0/1] " Hans Verkuil
2020-03-12 9:03 ` Dmitry Sepp [this message]
2020-03-12 9:49 ` Keiichi Watanabe
2020-03-12 9:54 ` Hans Verkuil
2020-03-12 10:11 ` Keiichi Watanabe
2020-03-12 10:29 ` Dmitry Sepp
2020-03-12 10:37 ` Hans Verkuil
2020-03-13 2:29 ` Nicolas Dufresne
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=3182728.aeNJFYEL58@os-lin-dmo \
--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