From: Detlev Casanova <detlev.casanova@collabora.com>
To: linux-kernel@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Fritz Koenig <frkoenig@chromium.org>,
Hans Verkuil <hverkuil@kernel.org>,
Sebastian Fricke <sebastian.fricke@collabora.com>,
Daniel Almeida <daniel.almeida@collabora.com>,
Detlev Casanova <detlev.casanova@collabora.com>,
Ricardo Ribalda <ribalda@chromium.org>,
Hans de Goede <hansg@kernel.org>, Yunke Cao <yunkec@google.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
James Cowgill <james.cowgill@blaize.com>,
linux-media@vger.kernel.org, kernel@collabora.com
Subject: [PATCH v2 0/2] media: Add HEVC long and short term ref pic sets controls
Date: Thu, 24 Jul 2025 14:10:17 -0400 [thread overview]
Message-ID: <20250724181019.242514-1-detlev.casanova@collabora.com> (raw)
New v4l2 controls for HEVC are added to be able to send the missing long
and short term RPS information to the driver.
Both controls have a dynamic size to send up to 65 sets each.
The controls take raw data as they are read from the video stream.
Detlev Casanova (2):
media: uapi: HEVC: Add v4l2_ctrl_hevc_ext_sps_[ls]t_rps controls
media: v4l2-ctrls: Add hevc_ext_sps_[ls]t_rps controls
.../media/v4l/ext-ctrls-codec-stateless.rst | 114 ++++++++++++++++++
.../media/v4l/vidioc-queryctrl.rst | 12 ++
drivers/media/v4l2-core/v4l2-ctrls-core.c | 18 +++
drivers/media/v4l2-core/v4l2-ctrls-defs.c | 10 ++
include/uapi/linux/v4l2-controls.h | 61 ++++++++++
include/uapi/linux/videodev2.h | 2 +
6 files changed, 217 insertions(+)
--
2.50.1
next reply other threads:[~2025-07-24 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 18:10 Detlev Casanova [this message]
2025-07-24 18:10 ` [PATCH v2 1/2] media: uapi: HEVC: Add v4l2_ctrl_hevc_ext_sps_[ls]t_rps controls Detlev Casanova
2025-07-24 18:10 ` [PATCH v2 2/2] media: v4l2-ctrls: Add hevc_ext_sps_[ls]t_rps controls Detlev Casanova
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=20250724181019.242514-1-detlev.casanova@collabora.com \
--to=detlev.casanova@collabora.com \
--cc=daniel.almeida@collabora.com \
--cc=frkoenig@chromium.org \
--cc=hansg@kernel.org \
--cc=hverkuil@kernel.org \
--cc=james.cowgill@blaize.com \
--cc=kernel@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sebastian.fricke@collabora.com \
--cc=senozhatsky@chromium.org \
--cc=yunkec@google.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®