From: Hans Verkuil <hverkuil@xs4all.nl>
To: linux-media@vger.kernel.org
Subject: [RFCv3 PATCH 0/2] Add VIDIOC_SUBDEV_QUERYCAP
Date: Thu, 2 Jul 2015 15:27:48 +0200 [thread overview]
Message-ID: <cover.1435842920.git.hans.verkuil@cisco.com> (raw)
From: Hans Verkuil <hans.verkuil@cisco.com>
This patch series adds the VIDIOC_SUBDEV_QUERYCAP ioctl for v4l-subdev devices
as discussed during the ELC in San Jose and as discussed here:
http://www.spinics.net/lists/linux-media/msg88009.html
This patch series returns to the v1 patch series, but it drops the pads field
and the VIDIOC_QUERYCAP changes.
This should hopefully make this a minimal uncontroversial implementation that
I can finally start using in the v4l2-compliance utility.
Ideally I'd like to have a link back to the media controller, which is what
the v2 patch series was all about, but not everyone agrees so I will probably
require that when v4l2-compliance is called for a v4l-subdev node you also
have to provide the MC device node.
Regards,
Hans
Hans Verkuil (2):
v4l2-subdev: add VIDIOC_SUBDEV_QUERYCAP ioctl
DocBook/media: document VIDIOC_SUBDEV_QUERYCAP
Documentation/DocBook/media/v4l/v4l2.xml | 1 +
.../DocBook/media/v4l/vidioc-subdev-querycap.xml | 133 +++++++++++++++++++++
drivers/media/v4l2-core/v4l2-subdev.c | 17 +++
include/uapi/linux/v4l2-subdev.h | 18 +++
4 files changed, 169 insertions(+)
create mode 100644 Documentation/DocBook/media/v4l/vidioc-subdev-querycap.xml
--
2.1.4
next reply other threads:[~2015-07-02 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 13:27 Hans Verkuil [this message]
2015-07-02 13:27 ` [RFCv3 PATCH 1/2] v4l2-subdev: add VIDIOC_SUBDEV_QUERYCAP ioctl Hans Verkuil
2015-07-02 13:27 ` [RFCv3 PATCH 2/2] DocBook/media: document VIDIOC_SUBDEV_QUERYCAP Hans Verkuil
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=cover.1435842920.git.hans.verkuil@cisco.com \
--to=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
/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