[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200622015227.24134-1-yunfei.dong@mediatek.com>
Date: Mon, 22 Jun 2020 09:52:25 +0800
From: Yunfei Dong <yunfei.dong@...iatek.com>
To: Hans Verkuil <hverkuil@...all.nl>,
Tiffany Lin <tiffany.lin@...iatek.com>,
Rob Herring <robh+dt@...nel.org>
CC: Yunfei Dong <yunfei.dong@...iatek.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Matthias Brugger <matthias.bgg@...il.com>,
<linux-media@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>,
Tomasz Figa <tfiga@...omium.org>
Subject: [PATCH v2, 0/2] This patchset add Read-only(Ro) request for capture queue
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(-)
Powered by blists - more mailing lists