From: Hans Verkuil <hverkuil@xs4all.nl>
To: Neil Armstrong <narmstrong@baylibre.com>,
mchehab@kernel.org, hans.verkuil@cisco.com
Cc: linux-media@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Maxime Jourdan <mjourdan@baylibre.com>
Subject: Re: [PATCH v3 2/4] media: vicodec: use v4l2-mem2mem draining, stopped and next-buf-is-last states handling
Date: Fri, 13 Dec 2019 14:21:26 +0100 [thread overview]
Message-ID: <0eb52de8-97a9-40cf-a926-262b1ecdc3e9@xs4all.nl> (raw)
In-Reply-To: <20191209122028.13714-3-narmstrong@baylibre.com>
On 12/9/19 1:20 PM, Neil Armstrong wrote:
> Use the previously introduced v4l2-mem2mem core APIs to handle the drainig,
> stopped and next-buf-is-last states.
>
> With these changes, the v4l2-compliance still passes with the following
> commands :
> # v4l2-ctl --stream-mmap --stream-out-mmap --stream-to-hdr out.comp --stream-from in.yuv
>>>>> <><><><><><><><><><><><><><><><>< 15.53 fps
> 15.53 fps
>> <><><><><><><><><><><><>< 13.99 fps
> 13.99 fps
>> <><><><><><><><><><><>< 13.52 fps
> 13.52 fps
>> <><><><><><><><><><><><>< 13.41 fps
> 13.41 fps
>> <><><><><><><><><><><><>< 13.21 fps
> 13.21 fps
>> <><><><><><><><><><><>< 13.09 fps
> 13.09 fps
>> <><><><><><><
> STOP ENCODER
> <<<
> EOS EVENT
>
> # v4l2-compliance --stream-from in.yuv -s
> v4l2-compliance SHA: 7ead0e1856b89f2e19369af452bb03fd0cd16793, 64 bits
> [...]
> Total for vicodec device /dev/video0: 50, Succeeded: 50, Failed: 0, Warnings: 0
>
> The full output is available at [1]
>
> # v4l2-compliance -d1 --stream-from-hdr out.comp -s
> v4l2-compliance SHA: 7ead0e1856b89f2e19369af452bb03fd0cd16793, 64 bits
> [...]
> Total for vicodec device /dev/video1: 50, Succeeded: 50, Failed: 0, Warnings: 0
>
> The full output is available at [2]
>
> No functional changes should be noticed.
Ah, unfortunately there *are* functional changes.
There is a (much) more extensive test that is done in the test-media script.
In v4l-utils, go to contrib/test. Now run (as root): test-media vicodec
This test now fails on some tests for the stateful decoder:
Streaming ioctls:
test read/write: OK (Not Supported)
test blocking wait: OK
fail: v4l2-test-buffers.cpp(943): ret == 0
fail: v4l2-test-buffers.cpp(1353): captureBufs(node, node_m2m_cap, q, m2m_q, frame_count, pollmode, capture_count)
test MMAP (select): FAIL
fail: v4l2-test-buffers.cpp(951): ret == 0
fail: v4l2-test-buffers.cpp(1353): captureBufs(node, node_m2m_cap, q, m2m_q, frame_count, pollmode, capture_count)
test MMAP (epoll): FAIL
fail: v4l2-test-buffers.cpp(943): ret == 0
fail: v4l2-test-buffers.cpp(1607): captureBufs(node, node_m2m_cap, q, m2m_q, frame_count, pollmode, capture_count)
test USERPTR (select): FAIL
fail: v4l2-test-buffers.cpp(943): ret == 0
fail: v4l2-test-buffers.cpp(1761): captureBufs(node, node_m2m_cap, q, m2m_q, frame_count, pollmode, capture_count)
test DMABUF (select): FAIL
I also see this:
cmp: EOF on /tmp/tmp.7KAXKAIkVZ/raw.yu12.1280.24 after byte 23500800, in line 1
which shouldn't be there either.
I can recommend the test-media script: it can test all the virtual drivers and it is
part of the daily build to check for regressions.
Regards,
Hans
next prev parent reply other threads:[~2019-12-13 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 12:20 [PATCH v3 0/4] media: meson: vdec: Add compliant H264 support Neil Armstrong
2019-12-09 12:20 ` [PATCH v3 1/4] media: v4l2-mem2mem: handle draining, stopped and next-buf-is-last states Neil Armstrong
2019-12-09 12:20 ` [PATCH v3 2/4] media: vicodec: use v4l2-mem2mem draining, stopped and next-buf-is-last states handling Neil Armstrong
2019-12-13 13:21 ` Hans Verkuil [this message]
2019-12-13 13:25 ` Neil Armstrong
2019-12-09 12:20 ` [PATCH v3 3/4] media: meson: vdec: bring up to compliance Neil Armstrong
2019-12-09 12:20 ` [PATCH v3 4/4] media: meson: vdec: add H.264 decoding support Neil Armstrong
2019-12-10 3:42 ` [PATCH v3 0/4] media: meson: vdec: Add compliant H264 support Nicolas Dufresne
2019-12-10 8:50 ` Neil Armstrong
2019-12-17 9:13 ` Neil Armstrong
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=0eb52de8-97a9-40cf-a926-262b1ecdc3e9@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=hans.verkuil@cisco.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mjourdan@baylibre.com \
--cc=narmstrong@baylibre.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).