From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Helen Koike <helen.koike@collabora.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: [PATCH v3 0/5] v4l2-dev/ioctl: Add V4L2_CAP_IO_MC
Date: Mon, 13 Jan 2020 00:24:53 +0100 [thread overview]
Message-ID: <20200112232458.2844506-1-niklas.soderlund+renesas@ragnatech.se> (raw)
Hi,
First of this series is based on work done by Helen in 2017 [1], I have
synced with her that it's OK for me to takeover the work.
This series aims to reduce the amount of boiler plate code in video
device drivers who's inputs and/or outputs are controlled by the Media
Controller instead of the V4L2 API.
Patch 1/5 adds a new video device capability flag V4L2_CAP_IO_MC which
if set provides helper implementations for the enum inputs and outputs
ioctrls freeing the video device driver from the need to implement them.
It also adds a default handler for VIDIOC_{G,S}_{INPUT,OUTPUT} as
suggested by Hans in v1. This allows video drivers (disregarding of the
V4L2_CAP_IO_MC flag) to remove callbacks for these operations if they
only provide a single input/output.
Patch 2/5, 3/5, 4/5 and 5/5 converts the R-Car VIN and Intel IPU3
drivers to use the new default handlers and capability flag and delete
the now redundant boiler plate code. I'm sure more video device drivers
can make use of this new flag but as I can only test on these two
platforms I have limited my changes to those.
1. https://patchwork.linuxtv.org/patch/41857/
Niklas Söderlund (5):
v4l2-dev/ioctl: Add V4L2_CAP_IO_MC
rcar-vin: Use default VIDIOC_{G,S}_{INPUT,OUTPUT} handler
staging/intel-ipu3: Use default VIDIOC_{G,S}_{INPUT,OUTPUT} handler
rcar-vin: Make use of V4L2_CAP_IO_MC
staging/intel-ipu3: Make use of V4L2_CAP_IO_MC
.../media/uapi/v4l/vidioc-querycap.rst | 5 ++
.../media/videodev2.h.rst.exceptions | 1 +
drivers/media/platform/rcar-vin/rcar-v4l2.c | 32 +--------
drivers/media/v4l2-core/v4l2-dev.c | 19 +++--
drivers/media/v4l2-core/v4l2-ioctl.c | 69 +++++++++++++++++--
drivers/staging/media/ipu3/ipu3-v4l2.c | 60 +---------------
include/uapi/linux/videodev2.h | 2 +
7 files changed, 89 insertions(+), 99 deletions(-)
--
2.24.1
next reply other threads:[~2020-01-12 23:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 23:24 Niklas Söderlund [this message]
2020-01-12 23:24 ` [PATCH v3 1/5] v4l2-dev/ioctl: Add V4L2_CAP_IO_MC Niklas Söderlund
2020-01-13 12:09 ` Sakari Ailus
2020-02-14 13:14 ` Hans Verkuil
2020-01-22 21:50 ` Helen Koike
2020-02-14 13:25 ` Hans Verkuil
2020-02-14 14:06 ` Helen Koike
2020-02-14 13:29 ` Hans Verkuil
2020-01-12 23:24 ` [PATCH v3 2/5] rcar-vin: Use default VIDIOC_{G,S}_{INPUT,OUTPUT} handler Niklas Söderlund
2020-01-12 23:24 ` [PATCH v3 3/5] staging/intel-ipu3: " Niklas Söderlund
2020-01-12 23:24 ` [PATCH v3 4/5] rcar-vin: Make use of V4L2_CAP_IO_MC Niklas Söderlund
2020-01-12 23:24 ` [PATCH v3 5/5] staging/intel-ipu3: " Niklas Söderlund
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=20200112232458.2844506-1-niklas.soderlund+renesas@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=helen.koike@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).