From: Gary Thomas <gary@mlbassoc.com>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Cc: linux-omap@vger.kernel.org
Subject: v4l2_int_device vs v4l2_subdev?
Date: Thu, 25 Jun 2009 16:43:03 -0600 [thread overview]
Message-ID: <4A43FD77.1020709@mlbassoc.com> (raw)
Still trying to wrap my head around the OMAP/34xx camera support.
I need to use the TVP5150 sensor/controller, but the existing
driver uses v4l_subdev. The "working" examples I've found
(from Sergio's tree) use sensors like ov3640 with uses v4l2_int_device
Are these two totally separate beasts?
If I have an infrastructure (I assume) based on v4l2_int_device,
how do I use a v4l2_subdev device driver? or need I move one to
the other?
... dizzy from traveling down too many twisty little passages :-(
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2009-06-25 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 22:43 Gary Thomas [this message]
2009-06-26 5:27 ` v4l2_int_device vs v4l2_subdev? Dongsoo, Nathaniel Kim
2009-06-26 6:30 ` Hans Verkuil
2009-06-26 14:43 ` Aguirre Rodriguez, Sergio Alberto
2009-06-27 12:58 ` 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=4A43FD77.1020709@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@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