From: Stanimir Varbanov <stanimir.varbanov@linaro.org>
To: Tomasz Figa <tfiga@chromium.org>, linux-media@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Hans Verkuil" <hverkuil@xs4all.nl>,
"Paweł Ościak" <posciak@chromium.org>,
"Alexandre Courbot" <acourbot@chromium.org>,
"Kamil Debski" <kamil@wypas.org>,
"Andrzej Hajda" <a.hajda@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Jeongtae Park" <jtp.park@samsung.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Tiffany Lin" <tiffany.lin@mediatek.com>,
"Andrew-CT Chen" <andrew-ct.chen@mediatek.com>,
"Stanimir Varbanov" <stanimir.varbanov@linaro.org>,
"Todor Tomov" <todor.tomov@linaro.org>,
"Nicolas Dufresne" <nicolas@ndufresne.ca>,
"Paul Kocialkowski" <paul.kocialkowski@bootlin.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
dave.stevenson@raspberrypi.org,
"Ezequiel Garcia" <ezequiel@collabora.com>,
"Maxime Jourdan" <maxi.jourdan@wanadoo.fr>
Subject: Re: [PATCH v2 1/2] media: docs-rst: Document memory-to-memory video decoder interface
Date: Mon, 12 Nov 2018 17:04:06 +0200 [thread overview]
Message-ID: <95f49917-5051-4604-63ea-ba3966d5179e@linaro.org> (raw)
In-Reply-To: <20181022144901.113852-2-tfiga@chromium.org>
Hi Tomasz,
On 10/22/18 5:48 PM, Tomasz Figa wrote:
> Due to complexity of the video decoding process, the V4L2 drivers of
> stateful decoder hardware require specific sequences of V4L2 API calls
> to be followed. These include capability enumeration, initialization,
> decoding, seek, pause, dynamic resolution change, drain and end of
> stream.
>
> Specifics of the above have been discussed during Media Workshops at
> LinuxCon Europe 2012 in Barcelona and then later Embedded Linux
> Conference Europe 2014 in Düsseldorf. The de facto Codec API that
> originated at those events was later implemented by the drivers we already
> have merged in mainline, such as s5p-mfc or coda.
>
> The only thing missing was the real specification included as a part of
> Linux Media documentation. Fix it now and document the decoder part of
> the Codec API.
>
> Signed-off-by: Tomasz Figa <tfiga@chromium.org>
> ---
> Documentation/media/uapi/v4l/dev-decoder.rst | 1082 +++++++++++++++++
> Documentation/media/uapi/v4l/devices.rst | 1 +
> Documentation/media/uapi/v4l/pixfmt-v4l2.rst | 5 +
> Documentation/media/uapi/v4l/v4l2.rst | 10 +-
> .../media/uapi/v4l/vidioc-decoder-cmd.rst | 40 +-
> Documentation/media/uapi/v4l/vidioc-g-fmt.rst | 14 +
> 6 files changed, 1137 insertions(+), 15 deletions(-)
> create mode 100644 Documentation/media/uapi/v4l/dev-decoder.rst
>
> diff --git a/Documentation/media/uapi/v4l/dev-decoder.rst b/Documentation/media/uapi/v4l/dev-decoder.rst
> new file mode 100644
> index 000000000000..09c7a6621b8e
> --- /dev/null
> +++ b/Documentation/media/uapi/v4l/dev-decoder.rst
> +State machine
> +=============
> +
> +.. kernel-render:: DOT
> + :alt: DOT digraph of decoder state machine
> + :caption: Decoder state machine
> +
> + digraph decoder_state_machine {
> + node [shape = doublecircle, label="Decoding"] Decoding;
> +
> + node [shape = circle, label="Initialization"] Initialization;
> + node [shape = circle, label="Capture\nsetup"] CaptureSetup;
> + node [shape = circle, label="Dynamic\nresolution\nchange"] ResChange;
> + node [shape = circle, label="Stopped"] Stopped;
> + node [shape = circle, label="Drain"] Drain;
> + node [shape = circle, label="Seek"] Seek;
> + node [shape = circle, label="End of stream"] EoS;
> +
> + node [shape = point]; qi
> + qi -> Initialization [ label = "open()" ];
> +
> + Initialization -> CaptureSetup [ label = "CAPTURE\nformat\nestablished" ];
> +
> + CaptureSetup -> Stopped [ label = "CAPTURE\nbuffers\nready" ];
> +
> + Decoding -> ResChange [ label = "Stream\nresolution\nchange" ];
> + Decoding -> Drain [ label = "V4L2_DEC_CMD_STOP" ];
> + Decoding -> EoS [ label = "EoS mark\nin the stream" ];
> + Decoding -> Seek [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];
> + Decoding -> Stopped [ label = "VIDIOC_STREAMOFF(CAPTURE)" ];
> + Decoding -> Decoding;
> +
> + ResChange -> CaptureSetup [ label = "CAPTURE\nformat\nestablished" ];
> + ResChange -> Seek [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];
> +
> + EoS -> Drain [ label = "Implicit\ndrain" ];
> +
> + Drain -> Stopped [ label = "All CAPTURE\nbuffers dequeued\nor\nVIDIOC_STREAMOFF(CAPTURE)" ];
> + Drain -> Seek [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];
> +
> + Seek -> Decoding [ label = "VIDIOC_STREAMON(OUTPUT)" ];
> + Seek -> Initialization [ label = "VIDIOC_REQBUFS(OUTPUT, 0)" ];
Shouldn't this be [ label = "VIDIOC_STREAMOFF(CAPTURE)" ], for me it is
looks more natural for v4l2?
For example I want to exit immediately from decoding state with calls to
streamoff(OUTPUT) and streamoff(CAPTURE). This could be when you press
ctrl-c while playing video, in this case I don't expect EoS nor buffers
draining.
> +
> + Stopped -> Decoding [ label = "V4L2_DEC_CMD_START\nor\nVIDIOC_STREAMON(CAPTURE)" ];
> + Stopped -> Seek [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];
> + }
> +
--
regards,
Stan
next prev parent reply other threads:[~2018-11-12 15:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 14:48 [PATCH v2 0/2] Document memory-to-memory video codec interfaces Tomasz Figa
2018-10-22 14:48 ` [PATCH v2 1/2] media: docs-rst: Document memory-to-memory video decoder interface Tomasz Figa
2018-10-29 9:45 ` Stanimir Varbanov
2018-10-29 10:06 ` Tomasz Figa
2018-10-29 10:07 ` Tomasz Figa
2018-11-12 11:37 ` Hans Verkuil
2019-01-22 10:02 ` Tomasz Figa
2019-01-22 14:47 ` Hans Verkuil
2019-01-23 5:27 ` Tomasz Figa
2019-01-23 8:10 ` Hans Verkuil
2019-01-24 9:06 ` Tomasz Figa
2019-01-24 19:55 ` Nicolas Dufresne
2019-01-25 3:27 ` Tomasz Figa
2019-01-30 4:02 ` Nicolas Dufresne
2019-02-06 5:35 ` Tomasz Figa
2019-04-09 9:47 ` Tomasz Figa
2019-04-10 9:26 ` Hans Verkuil
2018-11-12 15:04 ` Stanimir Varbanov [this message]
2018-11-15 14:34 ` Hans Verkuil
2018-11-17 4:31 ` Nicolas Dufresne
2018-11-17 11:43 ` Hans Verkuil
2018-11-18 1:25 ` Nicolas Dufresne
2018-10-22 14:49 ` [PATCH v2 2/2] media: docs-rst: Document memory-to-memory video encoder interface Tomasz Figa
2018-11-12 13:23 ` Hans Verkuil
2018-11-17 4:18 ` Nicolas Dufresne
2018-11-17 11:37 ` Hans Verkuil
2018-11-18 1:34 ` Nicolas Dufresne
2019-01-23 10:02 ` Tomasz Figa
2019-01-24 20:02 ` Nicolas Dufresne
2019-01-23 10:00 ` Tomasz Figa
2019-01-23 11:28 ` Hans Verkuil
2019-01-24 20:04 ` Nicolas Dufresne
2019-01-25 3:29 ` Tomasz Figa
2019-01-23 9:52 ` Tomasz Figa
2019-01-23 13:04 ` Hans Verkuil
2019-01-24 20:14 ` Nicolas Dufresne
2019-01-25 3:59 ` Tomasz Figa
2019-01-30 15:06 ` Nicolas Dufresne
2019-02-06 5:49 ` Tomasz Figa
2018-10-22 15:41 ` [PATCH v2 0/2] Document memory-to-memory video codec interfaces Hans Verkuil
2018-10-23 0:54 ` Tomasz Figa
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=95f49917-5051-4604-63ea-ba3966d5179e@linaro.org \
--to=stanimir.varbanov@linaro.org \
--cc=a.hajda@samsung.com \
--cc=acourbot@chromium.org \
--cc=andrew-ct.chen@mediatek.com \
--cc=dave.stevenson@raspberrypi.org \
--cc=ezequiel@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=jtp.park@samsung.com \
--cc=kamil@wypas.org \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maxi.jourdan@wanadoo.fr \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
--cc=paul.kocialkowski@bootlin.com \
--cc=posciak@chromium.org \
--cc=tfiga@chromium.org \
--cc=tiffany.lin@mediatek.com \
--cc=todor.tomov@linaro.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
all inboxes | Powered by JetHome®