From: Benjamin Gaignard <benjamin.gaignard@collabora.com>
To: mchehab@kernel.org, p.zabel@pengutronix.de,
hverkuil-cisco@xs4all.nl, nicolas.dufresne@collabora.com
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, kernel@collabora.com,
Benjamin Gaignard <benjamin.gaignard@collabora.com>
Subject: [RCF 0/2] Enumerate all pixels formats
Date: Thu, 11 Jan 2024 17:07:19 +0100 [thread overview]
Message-ID: <20240111160721.50020-1-benjamin.gaignard@collabora.com> (raw)
The goal of this series is to let userland applications enumerate
all the supported pixels formats of a stateless decoder without
setting all the possible codec-dependent control.
That offer a simplest solution for applications to discover
supported pixels formats and possibly let them doing smarter
choice between stateless decoders.
Benjamin
Benjamin Gaignard (2):
media: videodev2: Add V4L2_FMT_FLAG_ALL_FORMATS flag
media: verisilicon: Use V4L2_FMT_FLAG_ALL_FORMATS flag
.../media/v4l/dev-stateless-decoder.rst | 3 +++
.../userspace-api/media/v4l/vidioc-enum-fmt.rst | 4 ++++
.../userspace-api/media/videodev2.h.rst.exceptions | 1 +
drivers/media/platform/verisilicon/hantro_v4l2.c | 12 +++++++++---
drivers/media/v4l2-core/v4l2-ioctl.c | 2 +-
include/uapi/linux/videodev2.h | 1 +
6 files changed, 19 insertions(+), 4 deletions(-)
--
2.40.1
next reply other threads:[~2024-01-11 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 16:07 Benjamin Gaignard [this message]
2024-01-11 16:07 ` [RCF 1/2] media: videodev2: Add V4L2_FMT_FLAG_ALL_FORMATS flag Benjamin Gaignard
2024-01-17 19:41 ` Nicolas Dufresne
2024-01-31 10:06 ` Benjamin Gaignard
2024-01-11 16:07 ` [RCF 2/2] media: verisilicon: Use " Benjamin Gaignard
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=20240111160721.50020-1-benjamin.gaignard@collabora.com \
--to=benjamin.gaignard@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=p.zabel@pengutronix.de \
/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®