Re: OMAP 3530 camera ISP forks and new media framework

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

 



Hello Laurent,

2010/10/11 Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>:
> Hi Bastian,
>
> On Monday 11 October 2010 16:58:35 Bastian Hecht wrote:
>> 2010/10/11 Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>:
>> > On Monday 11 October 2010 14:59:15 Bastian Hecht wrote:
>> >> So... let's see if i got some things right, please let me now if you
>> >> disagree:
>> >>
>> >> - I do want to use the omap34xxcam.c driver as it is for the newest
>> >> framework and I get most support for it
>> >
>> > That's a bad start. With the latest driver, omap34xxcam.c doesn't exist
>> > anymore :-)
>>
>> Nice :S
>>
>> I think I take the mt9t001 approach (Sorry Guennadi, I think modifying
>> your framework is too much for me to start with). So in this driver I
>> tell the framework that I can do i2c probing, some subdev_core_ops and
>> some subdev_video_ops. I define these functions that mostly do some
>> basic i2c communication to the sensor chip. I guess I can handle that
>> as there are so many examples out there.
>
> The best solution would be to add mt9p031 support to the mt9t001 driver. If
> that's too difficult to start with, you can copy mt9t001 to mt9p031 and modify
> the driver as needed and merge the two drivers when you will be satisfied with
> the result.
>

OK, now I built the nokia kernel for the omap3-isp and made your
mt9t001.c work for it.
In mt9t001.c you call i2c_add_driver(&mt9t001_driver);
As far I as I figured out the driver core system looks for matches
between registered devices in arch/arm/omap/devices.c and appropriate
drivers.
Is the next step to include a static struct platform_device into
devices.c? Or is there a special i2c_device struct that I have to use?

Thanks so much,

 Bastian



>> But where do I stack that on top? On the camera bridge host, but if it
>> isn't omap34xxcam, which driver can I use? How are they connected?
>
> http://gitorious.org/maemo-multimedia/omap3isp-rx51
>
> The omap34xxcam.ko and isp-mod.ko modules have been merged into a single
> omap3-isp.ko module. All the driver code is now in drivers/media/video/isp.
>
> --
> Regards,
>
> Laurent Pinchart
>
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux