DongSoo(Nathaniel) Kim wrote:
This is quite confusing because in case of mine, I wanna make switchable between different cameras attached to omap camera interface.
Currently the ISP doesn't have a very neat way of controlling its use. In the recent patches, there's a change that allows just one isp_get() --- subsequent calls return -EBUSY.
So in practice, if you open the first device, you can't open the second one before the first one is closed. That's not very elegant but at least it prevents problematic concurrent access to the ISP.
In theory (AFAIK) the ISP *can* be used to receive data from multiple sources at the same time, but there are limitations.
In practice, if you have a hardware mux, you can switch it to a specific sensor when the camera driver tells the slave to go to some state that's not V4L2_POWER_OFF.
Which idea do I have to follow? Comparing with multiple video input devices and multiple cameras attached to single camera interface is giving me no answer. Perhaps multiple cameras with single camera interface couldn't make sense at the first place because single camera interface can go with only one camera module at one time. But we are using like that. I mean dual cameras with single camera interface. There is no choice except that when we are using dual camera without stereo camera controller.
Yup, I know, some mobile devices have front and back cameras. :)
By the way, I cannot find any API documents about VIDIOC_INT_S_VIDEO_ROUTING but it seems to be all about "how to route between input device with output device".
That, I guess, is meant for video output devices.
What exactly I need is "how to make switchable with multiple camera as an input for camera interface", which means just about an input device. In my opinion, those are different issues each other..(Am I right?) Cheers,
-- Sakari Ailus sakari.ai...@maxwell.research.nokia.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
