From: Hans Verkuil <hverkuil@xs4all.nl>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] Add VIDIOC_SUBDEV_QUERYCAP
Date: Mon, 04 May 2015 10:06:11 +0200 [thread overview]
Message-ID: <55472873.3010601@xs4all.nl> (raw)
In-Reply-To: <5300971.JLUFHG4Si2@avalon>
On 05/04/2015 12:33 AM, Laurent Pinchart wrote:
> Hi Hans,
>
> On Friday 01 May 2015 13:41:03 Hans Verkuil wrote:
>> On 05/01/2015 01:33 PM, Hans Verkuil wrote:
>>> 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
>>>
>>> It also adds the entity_id to v4l2_capability.
>>
>> Question: why do we have CONFIG_VIDEO_V4L2_SUBDEV_API? I don't really see
>> the point of this and I would propose to remove this config option and
>> instead use CONFIG_MEDIA_CONTROLLER.
>>
>> I don't see the use-case of having MEDIA_CONTROLLER defined but not
>> VIDEO_V4L2_SUBDEV_API.
>>
>> Comments?
>
> The idea is to compile the subdev userspace API code out when not needed. Not
> all media controller drivers need that API.
Sure, but it is not a lot of code, and I think it is somewhat confusing.
Just my opinion, though.
Hans
>
>>> Hans Verkuil (3):
>>> v4l2-subdev: add VIDIOC_SUBDEV_QUERYCAP ioctl
>>> DocBook/media: document VIDIOC_SUBDEV_QUERYCAP
>>> videodev2.h: add entity_id to struct v4l2_capability
>>>
>>> Documentation/DocBook/media/v4l/v4l2.xml | 1 +
>>> .../DocBook/media/v4l/vidioc-querycap.xml | 18 ++-
>>> .../DocBook/media/v4l/vidioc-subdev-querycap.xml | 140 ++++++++++++++++
>>> drivers/media/v4l2-core/v4l2-ioctl.c | 7 ++
>>> drivers/media/v4l2-core/v4l2-subdev.c | 19 +++
>>> include/uapi/linux/v4l2-subdev.h | 12 ++
>>> include/uapi/linux/videodev2.h | 5 +-
>>> 7 files changed, 199 insertions(+), 3 deletions(-)
>>> create mode 100644
>>> Documentation/DocBook/media/v4l/vidioc-subdev-querycap.xml
>
prev parent reply other threads:[~2015-05-04 8:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 11:33 [RFC PATCH 0/3] Add VIDIOC_SUBDEV_QUERYCAP Hans Verkuil
2015-05-01 11:33 ` [RFC PATCH 1/3] v4l2-subdev: add VIDIOC_SUBDEV_QUERYCAP ioctl Hans Verkuil
2015-05-03 22:20 ` Laurent Pinchart
2015-05-04 8:04 ` Hans Verkuil
2015-07-02 13:01 ` Sakari Ailus
2015-07-02 13:07 ` Hans Verkuil
2015-05-01 11:33 ` [RFC PATCH 2/3] DocBook/media: document VIDIOC_SUBDEV_QUERYCAP Hans Verkuil
2015-05-03 22:29 ` Laurent Pinchart
2015-05-04 7:58 ` Hans Verkuil
2015-05-01 11:33 ` [RFC PATCH 3/3] videodev2.h: add entity_id to struct v4l2_capability Hans Verkuil
2015-05-03 22:31 ` Laurent Pinchart
2015-05-01 11:41 ` [RFC PATCH 0/3] Add VIDIOC_SUBDEV_QUERYCAP Hans Verkuil
2015-05-03 22:33 ` Laurent Pinchart
2015-05-04 8:06 ` Hans Verkuil [this message]
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=55472873.3010601@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--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