From: Philipp Zabel <p.zabel@pengutronix.de>
To: linux-media@vger.kernel.org
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Pawel Osciak <pawel@osciak.com>,
Kamil Debski <k.debski@samsung.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
kernel@pengutronix.de, Philipp Zabel <p.zabel@pengutronix.de>
Subject: [PATCH v3 0/5] Signalling last decoded frame by V4L2_BUF_FLAG_LAST and -EPIPE
Date: Fri, 6 Mar 2015 11:18:25 +0100 [thread overview]
Message-ID: <1425637110-12100-1-git-send-email-p.zabel@pengutronix.de> (raw)
At the V4L2 codec API session during ELC-E 2014, we agreed that for the decoder
draining flow, after a V4L2_DEC_CMD_STOP decoder command was issued, the last
decoded buffer should get dequeued with a V4L2_BUF_FLAG_LAST set. After that,
poll should immediately return and all following VIDIOC_DQBUF should return
-EPIPE until the stream is stopped or decoding continued via V4L2_DEC_CMD_START.
(or STREAMOFF/STREAMON).
Changes since v2:
- Made V4L2_BUF_FLAG_LAST known to trace events
regards
Philipp
Peter Seiderer (1):
[media] videodev2: Add V4L2_BUF_FLAG_LAST
Philipp Zabel (4):
[media] videobuf2: return -EPIPE from DQBUF after the last buffer
[media] coda: Set last buffer flag and fix EOS event
[media] s5p-mfc: Set last buffer flag
[media] DocBooc: mention mem2mem codecs for encoder/decoder commands
Documentation/DocBook/media/v4l/io.xml | 10 ++++++++
.../DocBook/media/v4l/vidioc-decoder-cmd.xml | 6 ++++-
.../DocBook/media/v4l/vidioc-encoder-cmd.xml | 5 +++-
Documentation/DocBook/media/v4l/vidioc-qbuf.xml | 8 +++++++
drivers/media/platform/coda/coda-bit.c | 4 ++--
drivers/media/platform/coda/coda-common.c | 27 +++++++++-------------
drivers/media/platform/coda/coda.h | 3 +++
drivers/media/platform/s5p-mfc/s5p_mfc.c | 1 +
drivers/media/v4l2-core/v4l2-mem2mem.c | 10 +++++++-
drivers/media/v4l2-core/videobuf2-core.c | 18 ++++++++++++++-
include/media/videobuf2-core.h | 10 ++++++++
include/trace/events/v4l2.h | 3 ++-
include/uapi/linux/videodev2.h | 2 ++
13 files changed, 84 insertions(+), 23 deletions(-)
--
2.1.4
next reply other threads:[~2015-03-06 10:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 10:18 Philipp Zabel [this message]
2015-03-06 10:18 ` [PATCH v3 1/5] [media] videodev2: Add V4L2_BUF_FLAG_LAST Philipp Zabel
2015-03-06 10:18 ` [PATCH v3 2/5] [media] videobuf2: return -EPIPE from DQBUF after the last buffer Philipp Zabel
2015-03-06 10:18 ` [PATCH v3 3/5] [media] coda: Set last buffer flag and fix EOS event Philipp Zabel
2015-03-06 10:18 ` [PATCH v3 4/5] [media] s5p-mfc: Set last buffer flag Philipp Zabel
2015-03-06 10:18 ` [PATCH v3 5/5] [media] DocBooc: mention mem2mem codecs for encoder/decoder commands Philipp Zabel
2015-03-17 10:46 ` [PATCH v3 0/5] Signalling last decoded frame by V4L2_BUF_FLAG_LAST and -EPIPE Philipp Zabel
2015-03-17 16:09 ` Hans Verkuil
2015-03-18 16:20 ` Kamil Debski
2015-03-18 16:27 ` Philipp Zabel
2015-04-07 14:44 ` Kamil Debski
2015-04-08 10:09 ` Hans Verkuil
2015-04-08 10:19 ` Pawel Osciak
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=1425637110-12100-1-git-send-email-p.zabel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=hverkuil@xs4all.nl \
--cc=k.debski@samsung.com \
--cc=kernel@pengutronix.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=pawel@osciak.com \
--cc=sakari.ailus@linux.intel.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).