From: Hans Verkuil <hverkuil@xs4all.nl>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: v4l <video4linux-list@redhat.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: Integrating v4l2_device/v4l2_subdev into the soc_camera framework
Date: Tue, 16 Dec 2008 10:21:58 +0100 [thread overview]
Message-ID: <200812161021.58430.hverkuil@xs4all.nl> (raw)
In-Reply-To: <20081215155715.7e8f34e9.ospite@studenti.unina.it>
On Monday 15 December 2008 15:57:14 Antonio Ospite wrote:
> On Mon, 15 Dec 2008 11:45:54 +0100
>
> Hans Verkuil <hverkuil@xs4all.nl> wrote:
> > Hi Guennadi,
> >
> > Now that the v4l2_device and v4l2_subdev structs are merged into
> > the master v4l-dvb repository it is time to look at what needs to
> > be done to integrate it into the soc-camera framework.
> >
> > The goal is to make the i2c sub-device drivers independent from how
> > they are used. That is, whether a sensor is used in an embedded
> > device or in a USB webcam or something else should not matter for
> > the sensor driver.
>
> Is something like this planned for gspca as well?
My understanding is that most if not all of the 'subdevices' used in
gspca are reversed engineered and as such can by definition only work
within gspca.
So in this case I see no need to move to the new structs. That said,
there is nothing that prevents gspca to start using these structs as
well, in particular since they will be extended over time to take care
of e.g. control processing, etc.
Note that it is easy (although not yet implemented since nobody needs it
right now) to add driver-specific ops to v4l2_subdev. This could be
ideal for gspca. So it is still possible to use the gspca-specific ops
while also being able at the same time to use the standard ops and
other features that the framework will offer in the future.
Regards,
Hans
--
Hans Verkuil - video4linux developer - sponsored by TANDBERG
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-12-16 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 10:45 Integrating v4l2_device/v4l2_subdev into the soc_camera framework Hans Verkuil
2008-12-15 14:57 ` Antonio Ospite
2008-12-16 9:21 ` Hans Verkuil [this message]
2008-12-16 9:37 ` Guennadi Liakhovetski
2008-12-16 9:50 ` 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=200812161021.58430.hverkuil@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=g.liakhovetski@gmx.de \
--cc=ospite@studenti.unina.it \
--cc=video4linux-list@redhat.com \
/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.