Machine Vision

Suman,

AFAIK we do not have readily available driver for MT9V032 on top of 2.6.32 based release (for V4L2-Int framework) which I am aware of.

The Camera driver which you are referring to is based on older framework (V4L2-Int) and we have already migrated from V4l2-Int framework (all 2.6.32 kernel release) to Media-controller framework (2.6.37 kernel releases) with 04.02.00.07 release.

As far as MT9V032 driver is concerned, the driver is available in main-line kernel but that is based on sub-dev model, you have to port it to V4L2-Int framework to make it work on your use-case.

Thanks,

Vaibhav

Hi Vaibhav,

Thanks for the reply.

My customer is ready for shifting over to the latest Framework.

They downloaded the 2.6.37 kernel source and there were drivers for MT9V032. But they were not able to select these drivers through menuconfig.

Please can you let us know about the below -

1. How to include these drivers in kernel. 

2. Detail procedure to port the sub-dev model drivers to V4L2-int framework.

Thanks

Suman.

Hi Suman,

>> My customer is ready for shifting over to the latest Framework.

[Vaibhav] I hope you understand pros and cons of this. This is new framework, so most of the standard application will not work as is. There will be some effort required to port them.

>> They downloaded the 2.6.37 kernel source and there were drivers for MT9V032. But they were not able to select these drivers through menuconfig.

[Vaibhav] From where you downloaded this kernel? Is it directly from Main-line or TI maintained Arago repo? I will answer your both the questions based on above information.

Thanks,

Vaibhav

Hi Vaibhav,

They have download the kernel(2.6.37) source (AM35x-OMAP35x-LINUX-PSP-04.02.00.07.tgz) from below link:

http://software-dl.ti.com/dsps/dsps_public_sw/psp/LinuxPSP/OMAP_04_02/04_02_00_07//exports/AM35x-OMAP35x-LINUX-PSP-04.02.00.07.tgz

Thanks

Suman.

Sorry for delayed response,

In that case the MT9V032 driver is not ported for media-controller framework, so you can not use it directly. You have to port it to media-controller framework.

Thanks,

Vaibhav

Hi Vaibhav,

Below reply from customer -

---------------------------------------------------------------------------------------------------------------------------------------------------

You told that we have to port the image sensor drivers to media control framework. We didn't clearly understood what you mean by porting to media control frame work. As per our understanding to port means that we have to edit the board-omap3-camera.c   so that it registers our sensor drivers and give us the access to sensor in user’s space.

        On 2.6.32 there is v4l2 drivers and the document “video for Linux two API specifications”. Like this, is there any document for this new framework (Media control framework). We are unable to get information about media control framework.

        Now we are trying to interface an LI-5M03(MT9P031) instead of our aim MT9V032 on 2.6.37, because this module is already tested on 2.6.32. We think that if we are able to interface this sensor on 2.6.37 then it is very easy to us for our target module (MT9V032).

The above change reflects that it registers the drivers it generates /dev/video1 and /dev/video2.

.

.

.

.

[    4.124176] i2c /dev entries driver

[    4.133697] Linux media interface: v0.10

[    4.138549] Linux video capture interface: v2.00

[    4.146484] usbcore: registered new interface driver uvcvideo

[    4.152526] USB Video Class driver (v1.0.0)

.

.

.

if we tried to get capabilities using VIDIOC_QUERYCAP it gives 0x04000002 (it tells that it is video output device).

Are we on right track?

One more query that for target sensor(MT9V032) what is i2c slave ID we are tried 0x5C is this correct where to check.

Because we did not get chip_id on this adress.

---------------------------------------------------------------------------------------------------------------------------------------------------

Thanks

Suman.

Hi Vaibhav,

Have you been able to look into this?

Please do let me know.

Thanks

Suman.

Hi Vaibhav,

One update here -

Now customer is successful in communicating with target module mt9v032 over i2c bus. Now they can read the chip id on slave address 0x5c. 

Now they have a few questions on registering the device - 

-------------------------------------------------------------------------------------------------------------------

1. 1)      Which parameters of sensor to be passed to the kernel through these drivers and how?.

(we had supplied all necessary voltages to sensor separately so we don’t need to init regulators. Also the CLKIN(XCLK) have been supplied to  sensor independently )   

2. 2)      What differs to kernel  from sensor to sensor?

(According to our understanding the i2c address, register address and values, image height n width, pixel  format(image type),isp configuration)

3. 3)      What are the requirements of media control framework from image sensor.

 -------------------------------------------------------------------------------------------------------------------

Please do help sort out this issue. 

Thanks

Suman.

Hi Suman,

Based on the information above, I believe, customer has migrated to 2.6.37 based PSP release, right? Have you pointed them out to PSP UserGuide available on processor.wiki.com? If not, I would recommend to do so, since that should be starting point before jumping into kernel/driver implementation.

User Guide - http://processors.wiki.ti.com/index.php/UserGuideOmap35xCaptureDriver_PSP_04.02.00.07

Thanks,

Vaibhav