Re: mt9p031 support for Beagleboard.

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

 



Hi Vaibhav,

On Thursday 10 March 2011 17:23:52 Hiremath, Vaibhav wrote:
> On Thursday, March 10, 2011 9:31 PM Laurent Pinchart wrote: > > On Thursday 
10 March 2011 16:47:46 Hiremath, Vaibhav wrote:
> > > On Thursday, March 10, 2011 9:14 PM Laurent Pinchart wrote:
> > > > I'm curious about the Beagleboard code, as the camera module is an
> > > > expansion board you obviously can't hardcode support for it in the
> > > > board file. How do you plan to handle that ?
> > > 
> > > I did not understand your concern here, I already have MT9V113 sensor
> > > running with Media-controller (YUV format) on top of beagleXm board.
> > 
> > It's easy to patch the board-omap3beagle.c file to support the sensor,
> > but how can that patch be pushed to mainline ? We have a wide range of
> > sensors that can be connected to the Beagleboard, so this needs to be
> > somehow configurable.
> 
> Let me put my understanding here,
> 
> BeagleXM supports set of parallel sensors (MT9V113, MT9P031, MT9T111,
> etc...),  out of this I believe reset gpio, regulator and data channel
> path enable part is going to be common between all of the sensors.
> 
> The things which will be different would be, especially clock configuration
> and i2c address. I2C address is going to be very crucial and need some
> thinking, since there are sensors with same I2C address.

I2C addresses, signals polarities and data lane shifting will need to be 
configured.

> I guess I am still not following you completely (must be missing
> something), would you mind help me to understand your concern here.

Those parameters all need to be provided by board code. You can't push a patch 
that adds hardcoded support for the MT9P031 to the board-omap3beagled.c file 
upstream, as not all Beagleboards will have an MT9P031 sensor connected (or 
even any sensor at all). How can we push the code upstream and still make it 
configurable enough ?

> [By next week I should be able to make all my changes public (into my Arago
> repo) for reference]

There are too many repositories with code lying around. We should try to 
coordinate our efforts.

-- 
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