public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@nokia.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: "DongSoo(Nathaniel) Kim" <dongsoo.kim@gmail.com>,
	"Hiremath, Vaibhav" <hvaibhav@ti.com>,
	"Toivonen Tuukka.O (Nokia-D/Oulu)" <tuukka.o.toivonen@nokia.com>,
	"Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Nagalla, Hari" <hnagalla@ti.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [REVIEW PATCH 11/14] OMAP34XXCAM: Add driver
Date: Wed, 04 Mar 2009 21:22:04 +0200	[thread overview]
Message-ID: <49AED4DC.5050507@nokia.com> (raw)
In-Reply-To: <200903040839.48104.hverkuil@xs4all.nl>

Hans Verkuil wrote:
> On Wednesday 04 March 2009 01:42:13 DongSoo(Nathaniel) Kim wrote:
>> Thank you for your kind explanation Hans.
>>
>> Problem is omap3 camera subsystem is making device node for every int
>> device attached to it.
> 
> That's wrong. Multiple devices should only be created if they can all be 
> used at the same time. Otherwise there should be just one device that uses 
> S_INPUT et al to select between the inputs.

There might be situations where multiple device nodes would be 
beneficial even if they cannot be used simultaneously in all cases.

Currently the omap34xxcam camera driver creates one device per camera. A 
camera in this case contains an isp (or camera controller), image 
sensor, lens and flash. The properties like maximum frame rate or 
resolution of a camera are usually (almost) completely defined by those 
of the sensor, lens and flash. This affects also cropping capabilities.

Several programs can access video devices simultaneously. What happens 
if another program switches the input when the first one doesn't expect 
it? The original user won't notice the change, instead of getting -EBUSY 
when trying to open the other video device.

In short, it's been just more clear to have one device per camera. There 
may be other reasons but these come to mind this time.

> BTW, do I understand correctly that e.g. lens drivers also get their 
> own /dev/videoX node? Please tell me I'm mistaken! Since that would be so 
> very wrong.

Yes, you're mistaken this time. :)

The contents of a video devices are defined in platform data.

> I hope that the conversion to v4l2_subdev will take place soon. You are 
> basically stuck in a technological dead-end :-(

Making things working properly in camera and ISP drivers has taken much 
more time than was anticipated and v4l2_subdev framework has developed a 
lot during that time. You're right --- we'll start thinking of how and 
when to move to v4l2_subdev.

Thanks.

-- 
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com

  parent reply	other threads:[~2009-03-04 19:22 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5e9665e10903021848u328e0cd4m5186344be15b817@mail.gmail.com>
     [not found] ` <19F8576C6E063C45BE387C64729E73940427BC9B86@dbde02.ent.ti.com>
2009-03-03  5:13   ` [REVIEW PATCH 11/14] OMAP34XXCAM: Add driver DongSoo(Nathaniel) Kim
2009-03-03  7:36     ` Hans Verkuil
2009-03-04  0:42       ` DongSoo(Nathaniel) Kim
2009-03-04  7:39         ` Hans Verkuil
2009-03-04  7:49           ` Tuukka.O Toivonen
2009-03-04 19:22           ` Sakari Ailus [this message]
2009-03-04 21:05             ` Hans Verkuil
2009-03-04 21:46               ` Aguirre Rodriguez, Sergio Alberto
2009-03-04 22:44                 ` Hans Verkuil
2009-03-04 23:30                   ` Aguirre Rodriguez, Sergio Alberto
2009-03-05  7:39                     ` Hans Verkuil
2009-03-05 20:11                   ` Sakari Ailus
2009-03-05 21:24                     ` Hans Verkuil
2009-03-10 12:14                       ` Sakari Ailus
2009-03-04 23:42                 ` Trent Piepho
2009-03-05  2:25                   ` hermann pitton
2009-03-03  7:38     ` Sakari Ailus
2009-03-10 13:34 Hans Verkuil
  -- strict thread matches above, loose matches on Subject: below --
2009-03-04  8:12 Hans Verkuil
     [not found] <Acl1IyQQvIDQejCAQ5O/QnkHIBmt3w==>
2009-01-13  2:03 ` Aguirre Rodriguez, Sergio Alberto
2009-01-13  7:24   ` Hans Verkuil
2009-02-06  2:26   ` DongSoo Kim
2009-02-11  4:00   ` DongSoo Kim
2009-02-12  7:09     ` Sakari Ailus
2009-02-12  7:52       ` DongSoo Kim
2009-02-13  9:31         ` Arun KS
2009-02-13 10:04           ` DongSoo(Nathaniel) Kim
2009-02-13 10:02         ` Sakari Ailus
2009-02-13 10:11           ` DongSoo(Nathaniel) Kim
     [not found] <Aclb0Ghhhph2tRyARSuubB27tGfovg==>
2008-12-11 20:38 ` Aguirre Rodriguez, Sergio Alberto
2009-02-23  8:26   ` DongSoo(Nathaniel) Kim

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=49AED4DC.5050507@nokia.com \
    --to=sakari.ailus@nokia.com \
    --cc=dongsoo.kim@gmail.com \
    --cc=hnagalla@ti.com \
    --cc=hvaibhav@ti.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=saaguirre@ti.com \
    --cc=sakari.ailus@maxwell.research.nokia.com \
    --cc=tuukka.o.toivonen@nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox