diff options
| author | Benoit Parrot <bparrot@ti.com> | 2019-10-07 12:10:00 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab+samsung@kernel.org> | 2019-10-10 13:49:41 -0300 |
| commit | 2444846c0dbfa4ead21b621e4300ec32c90fbf38 (patch) | |
| tree | f07b7a196738fcfce2282ea4ed258d99a3d35775 /tools/perf/scripts/python/syscall-counts.py | |
| parent | 0bac73adea4df8d34048b38f6ff24dc3e73e90b6 (diff) | |
| download | linux-2444846c0dbfa4ead21b621e4300ec32c90fbf38.tar.gz linux-2444846c0dbfa4ead21b621e4300ec32c90fbf38.zip | |
media: ti-vpe: vpe: fix a v4l2-compliance failure about frame sequence number
v4l2-compliance fails with this message:
fail: v4l2-test-buffers.cpp(294): \
(int)g_sequence() < seq.last_seq + 1
fail: v4l2-test-buffers.cpp(740): \
buf.check(m2m_q, last_m2m_seq)
fail: v4l2-test-buffers.cpp(974): \
captureBufs(node, q, m2m_q, frame_count, true)
test MMAP: FAIL
The driver is failing to update the source frame sequence number in the
vb2 buffer object. Only the destination frame sequence was being
updated.
This is only a reporting issue if the user space app actually cares
about the frame sequence number. But it is fixed nonetheless.
Signed-off-by: Benoit Parrot <bparrot@ti.com>
Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions