From: Paul Kocialkowski <paulk@sys-base.io>
To: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Paul Kocialkowski <paulk@sys-base.io>
Subject: [PATCH v2 4/4] Documentation: media: Document V4L2_H264_DECODE_PARAM_FLAG_PFRAME/BFRAME
Date: Sun, 24 Aug 2025 20:07:35 +0200 [thread overview]
Message-ID: <20250824180735.765587-5-paulk@sys-base.io> (raw)
In-Reply-To: <20250824180735.765587-1-paulk@sys-base.io>
These flags are meant for a very specific use-case, add a mention of it.
Signed-off-by: Paul Kocialkowski <paulk@sys-base.io>
---
.../userspace-api/media/v4l/ext-ctrls-codec-stateless.rst | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst b/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst
index 0da635691fdc..de1e3873385c 100644
--- a/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst
+++ b/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst
@@ -618,10 +618,14 @@ Stateless Codec Control ID
-
* - ``V4L2_H264_DECODE_PARAM_FLAG_PFRAME``
- 0x00000008
- -
+ - All submitted slices for the frame are P slices. This is a compability
+ flag required for decoders that only support decoding such frames, but
+ should not be required for slice-based decoders.
* - ``V4L2_H264_DECODE_PARAM_FLAG_BFRAME``
- 0x00000010
- -
+ - All submitted slices for the frame are B slices. This is a compability
+ flag required for decoders that only support decoding such frames, but
+ should not be required for slice-based decoders.
.. raw:: latex
--
2.50.1
next prev parent reply other threads:[~2025-08-24 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 18:07 [PATCH v2 0/4] Minor V4L2 Headers and Codec Doc Cleanups Paul Kocialkowski
2025-08-24 18:07 ` [PATCH v2 1/4] media: uapi: Move colorimetry controls at the end of the file Paul Kocialkowski
2025-08-28 18:45 ` Nicolas Dufresne
2025-08-24 18:07 ` [PATCH v2 2/4] media: uapi: Cleanup tab after define in headers Paul Kocialkowski
2025-08-28 18:46 ` Nicolas Dufresne
2025-08-24 18:07 ` [PATCH v2 3/4] media: uapi: v4l2-controls: Cleanup codec definitions Paul Kocialkowski
2025-08-28 18:46 ` Nicolas Dufresne
2025-08-24 18:07 ` Paul Kocialkowski [this message]
2025-08-28 20:42 ` [PATCH v2 4/4] Documentation: media: Document V4L2_H264_DECODE_PARAM_FLAG_PFRAME/BFRAME Nicolas Dufresne
2025-08-29 14:15 ` Paul Kocialkowski
2025-08-30 11:29 ` Dmitry Osipenko
2025-08-29 20:40 ` [PATCH v2 0/4] Minor V4L2 Headers and Codec Doc Cleanups Nicolas Dufresne
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=20250824180735.765587-5-paulk@sys-base.io \
--to=paulk@sys-base.io \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.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
all inboxes | Powered by JetHome®