linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: linux-media@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
	Jean-Francois Moine <moinejf@free.fr>
Subject: Re: [PATCH 0/3] gspca: kinect cleanup, ov534 port to control framework
Date: Fri, 18 May 2012 14:30:49 +0200	[thread overview]
Message-ID: <4FB640F9.9030703@redhat.com> (raw)
In-Reply-To: <1337204566-2212-1-git-send-email-ospite@studenti.unina.it>

Hi,

Thanks for the patches. I've added them all to my tree, so
they will be included in my next pull-req. In the mean time
you can find them (unmodified) here:

http://git.linuxtv.org/hgoede/gspca.git/shortlog/refs/heads/media-for_v3.5-wip



On 05/16/2012 11:42 PM, Antonio Ospite wrote:
> Hi,
>
> the first patch just removes traces of the gspca control handling
> mechanism from the kinect driver; this driver does not have any
> controls. The change is trivial and can be applied right away, or
> postponed to when the gspca_main code is removed, you decide.
>
> The second patch removes the dependency between auto gain and auto white
> balance, I'd like to hear Jean-Francois on this, the webcam (the ov772x
> sensor) is able to set the two parameters independently and the user can
> see the difference of either, is there a reason why we were preventing
> the user from doing so before?
>
> The third patch is the conversion of the ov534 subdriver to the v4l2
> control framework, I tested the code with a PS3 Eye (ov772x sensor) and
> it works fine (now disabling automatic exposure works too, yay), maybe
> someone else can give it a run on a webcam with OV767x.
>
> NOTE: in patch 3, in sd_init_controls(), I left multiple checks
>
> 	if (sd->sensor == SENSOR_OV772x)
>
> just to preserve the order the controls were declared in "struct sd", if
> you feel the order is not that important I can aggregate the checks,
> just let me know, it just looked neater to me this way.
>
>
>  From a purely aesthetic point of view maybe the gspca mechanism of
> defining controls was prettier, more declarative, but the control
> framework really looks "more correct" even from userspace, qv4l2 can now
> display labels of control classes in tabs automatically while before we
> had empty labels, disabled controls in clusters work beautifully, and
> disabled controls with associated automatic settings can show the value
> calculated by the hardware on every update, very instructive if not
> super-useful.

I'm glad to hear you like the control framework.

Regards,

Hans


>
> Thanks,
>     Antonio
>
> Antonio Ospite (3):
>    gspca - kinect: remove traces of gspca control handling
>    gspca - ov534: make AGC and AWB controls independent
>    gspca - ov534: convert to v4l2 control framework
>
>   drivers/media/video/gspca/kinect.c |    9 -
>   drivers/media/video/gspca/ov534.c  |  590 ++++++++++++++++--------------------
>   2 files changed, 261 insertions(+), 338 deletions(-)
>

      parent reply	other threads:[~2012-05-18 12:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 21:42 [PATCH 0/3] gspca: kinect cleanup, ov534 port to control framework Antonio Ospite
2012-05-16 21:42 ` [PATCH 1/3] gspca_kinect: remove traces of the gspca control mechanism Antonio Ospite
2012-05-16 21:42 ` [PATCH 2/3] gspca_ov534: make AGC and AWB controls independent Antonio Ospite
2012-05-16 21:42 ` [PATCH 3/3] gspca_ov534: Convert to the control framework Antonio Ospite
2012-05-18  7:08 ` [PATCH 0/3] gspca: kinect cleanup, ov534 port to " Jean-Francois Moine
2012-05-18 11:38   ` Antonio Ospite
2012-05-18 12:30 ` Hans de Goede [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=4FB640F9.9030703@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=moinejf@free.fr \
    --cc=ospite@studenti.unina.it \
    /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).