All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [GIT PATCHES FOR 2.6.40] Make the UVC API public (and minor enhancements)
Date: Thu, 05 May 2011 08:33:20 -0300	[thread overview]
Message-ID: <4DC28B00.50505@redhat.com> (raw)
In-Reply-To: <201104271238.03887.laurent.pinchart@ideasonboard.com>

Em 27-04-2011 07:38, Laurent Pinchart escreveu:
> Hi Mauro,
> 
> These patches move the uvcvideo.h header file from drivers/media/video/uvc
> to include/linux, making the UVC API public. Support for the old API is kept
> and will be removed in 2.6.42.
> 
> The following changes since commit a4761a092fd3b6bf8b5f9cfe361670c86cdcc8ca:
> 
>   [media] tm6000: fix vbuf may be used uninitialized (2011-04-19 21:13:59 -0300)
> 
> are available in the git repository at:
>   git://linuxtv.org/pinchartl/uvcvideo.git uvcvideo-next
> 
> Laurent Pinchart (5):
>       uvcvideo: Deprecate UVCIOC_CTRL_{ADD,MAP_OLD,GET,SET}
>       uvcvideo: Rename UVC_CONTROL_* flags to UVC_CTRL_FLAG_*
>       uvcvideo: Make the API public

Why are you declaring this twice:

Index: patchwork/drivers/media/video/uvc/uvcvideo.h

...

+#ifndef __KERNEL__
 #define UVCIOC_CTRL_ADD              _IOW('U', 1, struct uvc_xu_control_info)
#define UVCIOC_CTRL_MAP_OLD  _IOWR('U', 2, struct uvc_xu_control_mapping_old)
 #define UVCIOC_CTRL_MAP              _IOWR('U', 2, struct uvc_xu_control_mapping)
 #define UVCIOC_CTRL_GET              _IOWR('U', 3, struct uvc_xu_control)
 #define UVCIOC_CTRL_SET        	_IOW('U', 4, struct uvc_xu_control)
-#define UVCIOC_CTRL_QUERY    _IOWR('U', 5, struct uvc_xu_control_query)
+#else
+#define __UVCIOC_CTRL_ADD    _IOW('U', 1, struct uvc_xu_control_info)
+#define __UVCIOC_CTRL_MAP_OLD        _IOWR('U', 2, struct uvc_xu_control_mapping_old)
+#define __UVCIOC_CTRL_MAP    _IOWR('U', 2, struct uvc_xu_control_mapping)
+#define __UVCIOC_CTRL_GET    _IOWR('U', 3, struct uvc_xu_control)
+#define __UVCIOC_CTRL_SET    _IOW('U', 4, struct uvc_xu_control)
+#endif

You shouldn't need to do that. In fact, the better would be to have two separate
headers: one with just the public API under include/linux, and another with the
extra uvc-internal bits, as we did in the past with videobuf2.h.

As the other patches don't depend on this one, I'm applying the remaining patches,
in order to save me the time of review the entire series again.

>       uvcvideo: Add support for V4L2_PIX_FMT_RGB565
>       uvcvideo: Add support for JMicron USB2.0 XGA WebCam
> 
> Martin Rubli (2):
>       uvcvideo: Add UVCIOC_CTRL_QUERY ioctl
>       uvcvideo: Add driver documentation
> 
>  Documentation/feature-removal-schedule.txt |   23 ++
>  Documentation/ioctl/ioctl-number.txt       |    2 +-
>  Documentation/video4linux/uvcvideo.txt     |  239 ++++++++++++++++++++
>  drivers/media/video/uvc/uvc_ctrl.c         |  332 +++++++++++++++++-----------
>  drivers/media/video/uvc/uvc_driver.c       |   14 ++
>  drivers/media/video/uvc/uvc_v4l2.c         |   51 ++++-
>  drivers/media/video/uvc/uvcvideo.h         |   57 ++++--
>  include/linux/Kbuild                       |    1 +
>  include/linux/uvcvideo.h                   |   69 ++++++
>  9 files changed, 625 insertions(+), 163 deletions(-)
>  create mode 100644 Documentation/video4linux/uvcvideo.txt
>  create mode 100644 include/linux/uvcvideo.h
> 


  reply	other threads:[~2011-05-05 11:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 10:38 [GIT PATCHES FOR 2.6.40] Make the UVC API public (and minor enhancements) Laurent Pinchart
2011-05-05 11:33 ` Mauro Carvalho Chehab [this message]
2011-05-05 11:40   ` Laurent Pinchart
2011-05-05 12:17     ` Mauro Carvalho Chehab
2011-05-05 12:27       ` Laurent Pinchart

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=4DC28B00.50505@redhat.com \
    --to=mchehab@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.