From: Yunfei Dong <yunfei.dong@mediatek.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Tiffany Lin <tiffany.lin@mediatek.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Yunfei Dong <yunfei.dong@mediatek.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
<linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
Tomasz Figa <tfiga@chromium.org>
Subject: [PATCH v2, 0/2] This patchset add Read-only(Ro) request for capture queue
Date: Mon, 22 Jun 2020 09:52:25 +0800 [thread overview]
Message-ID: <20200622015227.24134-1-yunfei.dong@mediatek.com> (raw)
User driver need to get HDR10+ information for each capture buffer;
For some encoder cases, user driver need to get encoded message for
each frame. So add support read-only(Ro) request for capture queue.
Ro request mean that user driver just can get ext ctrls, set ext ctrls
is not not allowed. Ro Request also can be used in output queue.
There is not upstream driver to use this feature at now, but we are
developing internal driver to use it. If it is ready, we will try to
upstream vdec/venc driver based on this feature.
Change compared to v1:
-change commit message of patch 01/02
-change commit message of patch 02/02
Yunfei Dong (2):
media: v4l UAPI: add V4L2_BUF_CAP_SUPPORTS_RO_REQUESTS
media: v4l: Add Ro request api for capture queue
.../media/v4l/vidioc-reqbufs.rst | 4 +
.../media/common/videobuf2/videobuf2-v4l2.c | 7 ++
drivers/media/mc/mc-request.c | 10 +-
drivers/media/v4l2-core/v4l2-ctrls.c | 107 +++++++++++++++---
drivers/media/v4l2-core/v4l2-ioctl.c | 22 ++++
drivers/media/v4l2-core/v4l2-mem2mem.c | 19 ++--
include/media/v4l2-ctrls.h | 22 +++-
include/media/v4l2-fh.h | 2 +
include/media/videobuf2-core.h | 2 +
include/uapi/linux/videodev2.h | 1 +
10 files changed, 158 insertions(+), 38 deletions(-)
next reply other threads:[~2020-06-22 1:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 1:52 Yunfei Dong [this message]
2020-06-22 1:52 ` [PATCH v2, 1/2] media: v4l UAPI: add V4L2_BUF_CAP_SUPPORTS_RO_REQUESTS Yunfei Dong
2020-06-22 1:52 ` [PATCH v2, 2/2] media: v4l: Add Ro request api for capture queue Yunfei Dong
2020-06-23 8:23 ` dikshita
2020-06-23 18:43 ` [PATCH v2, 0/2] This patchset add Read-only(Ro) request " Ezequiel Garcia
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=20200622015227.24134-1-yunfei.dong@mediatek.com \
--to=yunfei.dong@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tfiga@chromium.org \
--cc=tiffany.lin@mediatek.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®