Re: [REVIEW PATCH 11/14] OMAP34XXCAM: Add driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday 23 February 2009 10:08:54 ext DongSoo(Nathaniel) Kim wrote:
> So, logically it does not make sense with making device nodes of every
> single slave attached with OMAP3camera interface. Because they can't
> be opened at the same time,even if it is possible it should not work
> properly.
> 
> So.. how about making only single device node like /dev/video0 for
> OMAP3 camera interface and make it switchable through V4L2 API. Like
> VIDIOC_S_INPUT?

You are right that if the OMAP3 has several camera sensors attached
to its camera interface, generally just one can be used at once.

However, from user's perspective those are still distinct
cameras. Many v4l2 applications don't support VIDIOC_S_INPUT
or at least it will be more difficult to use than just pointing
an app to the correct video device. Logically they are two
independent cameras, which can't be used simultaneously
due to HW restrictions.

- Tuukka
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux