From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Nicolas Dufresne <nicolas@ndufresne.ca>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 3/3] media: docs: dev-stateless-decoder: Document frame type flags
Date: Sun, 16 Jan 2022 21:55:56 +0300 [thread overview]
Message-ID: <20220116185556.10657-4-digetx@gmail.com> (raw)
In-Reply-To: <20220116185556.10657-1-digetx@gmail.com>
Document that frame type flags must be set for the coded buffer.
Decoders, like NVIDIA Tegra h264 decoder for example, won't work
properly without these flags.
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
---
.../userspace-api/media/v4l/dev-stateless-decoder.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/userspace-api/media/v4l/dev-stateless-decoder.rst b/Documentation/userspace-api/media/v4l/dev-stateless-decoder.rst
index 4a26646eeec5..845f4481d34f 100644
--- a/Documentation/userspace-api/media/v4l/dev-stateless-decoder.rst
+++ b/Documentation/userspace-api/media/v4l/dev-stateless-decoder.rst
@@ -271,6 +271,9 @@ A typical frame would thus be decoded using the following sequence:
we are not sure that the current decode request is the last one needed
to produce a fully decoded frame, then
``V4L2_BUF_FLAG_M2M_HOLD_CAPTURE_BUF`` must also be set.
+ ``V4L2_BUF_FLAG_KEYFRAME``, ``V4L2_BUF_FLAG_PFRAME`` and
+ ``V4L2_BUF_FLAG_BFRAME`` must be set if relevant to the coded
+ format.
``request_fd``
must be set to the file descriptor of the decoding request.
--
2.33.1
next prev parent reply other threads:[~2022-01-16 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 18:55 [PATCH v2 0/3] Add V4L stateless video decoder API support to NVIDIA Tegra driver Dmitry Osipenko
2022-01-16 18:55 ` [PATCH v2 1/3] media: staging: tegra-vde: Factor out H.264 code Dmitry Osipenko
2022-01-16 18:55 ` [PATCH v2 2/3] media: staging: tegra-vde: Support V4L stateless video decoder API Dmitry Osipenko
2022-01-16 18:55 ` Dmitry Osipenko [this message]
2022-01-25 20:37 ` [PATCH v2 3/3] media: docs: dev-stateless-decoder: Document frame type flags Nicolas Dufresne
2022-01-26 12:33 ` Dmitry Osipenko
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=20220116185556.10657-4-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=hverkuil@xs4all.nl \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=thierry.reding@gmail.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).