[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220116185556.10657-4-digetx@gmail.com>
Date: Sun, 16 Jan 2022 21:55:56 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Hans Verkuil <hverkuil@...all.nl>,
Nicolas Dufresne <nicolas@...fresne.ca>,
Ezequiel Garcia <ezequiel@...guardiasur.com.ar>
Cc: linux-media@...r.kernel.org, linux-staging@...ts.linux.dev,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH v2 3/3] media: docs: dev-stateless-decoder: Document frame type flags
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@...il.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
Powered by blists - more mailing lists