From: Hans de Goede <hdegoede@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, Jean-Francois Moine <moinejf@free.fr>
Subject: Re: [RFCv1 PATCH 0/7] gspca: allow use of control framework and other fixes
Date: Mon, 30 Apr 2012 13:13:59 +0200 [thread overview]
Message-ID: <4F9E73F7.6040207@redhat.com> (raw)
In-Reply-To: <1335625796-9429-1-git-send-email-hverkuil@xs4all.nl>
Hi,
On 04/28/2012 05:09 PM, Hans Verkuil wrote:
> Hi all,
>
> Here is a patch series that makes it possible to use the control framework
> in gspca. The gspca core changes are very minor but as a bonus give you
> priority support as well.
>
> The hard work is in updating the subdrivers. I've done two, and I intend
> to do the stv06xx driver as well, but that's the last of my gspca webcams
> that I can test. Looking through the subdrivers I think that 50-70% are in
> the category 'easy to convert', the others will take a bit more time
> (autogain/gain type of constructs are always more complex than just a simple
> brightness control).
>
> After applying this patch series the two converted drivers pass the
> v4l2-compliance test as it stands today.
I haven't looked at any details yet, but from the description I love the changes :)
I was actually planning on doing something very similar myself soon-ish, so you've
saved me a bunch of work :)
I'll review this and add these to my tree. Jean-Francois, is it ok for these changes
to go upstream through my tree? The reason I'm asking is that I plan to convert
more subdrivers to the control framework for 3.5 and its easiest to have this all
in one tree then.
If you've remarks to the core changes I will make sure these get addressed in my
tree of course.
Regards,
Hans (the other Hans :)
next prev parent reply other threads:[~2012-04-30 11:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 15:09 [RFCv1 PATCH 0/7] gspca: allow use of control framework and other fixes Hans Verkuil
2012-04-28 15:09 ` [RFCv1 PATCH 1/7] gspca: allow subdrivers to use the control framework Hans Verkuil
2012-04-28 15:09 ` [RFCv1 PATCH 2/7] zc3xx: convert to " Hans Verkuil
2012-05-05 14:35 ` Hans de Goede
2012-04-28 15:09 ` [RFCv1 PATCH 3/7] sn9c20x: " Hans Verkuil
2012-04-28 15:09 ` [RFCv1 PATCH 4/7] gspca: use video_drvdata(file) instead of file->private_data Hans Verkuil
2012-04-28 15:09 ` [RFCv1 PATCH 5/7] gscpa: use v4l2_fh and add G/S_PRIORITY support Hans Verkuil
2012-04-28 15:09 ` [RFCv1 PATCH 6/7] gspca: add support for control events Hans Verkuil
2012-04-28 15:09 ` [RFCv1 PATCH 7/7] gspca: fix querycap and incorrect return codes Hans Verkuil
2012-05-05 7:43 ` [RFCv1 PATCH 1/7] gspca: allow subdrivers to use the control framework Hans de Goede
2012-05-05 8:34 ` Hans Verkuil
2012-05-05 14:46 ` Hans de Goede
2012-05-05 14:50 ` Hans Verkuil
2012-05-05 14:59 ` Hans de Goede
2012-05-05 17:20 ` Jean-Francois Moine
2012-05-05 9:14 ` Hans Verkuil
2012-05-05 14:44 ` Hans de Goede
2012-05-05 15:02 ` Hans Verkuil
2012-05-05 15:41 ` Hans de Goede
2012-05-05 15:05 ` Hans de Goede
2012-05-05 15:40 ` Hans de Goede
2012-05-05 17:24 ` Jean-Francois Moine
2012-04-30 11:13 ` Hans de Goede [this message]
2012-05-01 10:28 ` [RFCv1 PATCH 0/7] gspca: allow use of control framework and other fixes Jean-Francois Moine
2012-05-05 7:38 ` Hans de Goede
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=4F9E73F7.6040207@redhat.com \
--to=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=moinejf@free.fr \
/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.