On Wed, 10 Jun 2009, Karicheri, Muralidharan wrote: > Guennadi, > > Thanks for responding. I acknowledge I need to add > master & slave information in the structure. Querying > the capabilities from the sub device is a good feature. > I will look into your references and let you know if I > have any question. > > I will send an updated patch based on this. > > BTW, I have a question about the mt9t031.c driver. Could > I use this driver to stream VGA frames from the sensor? Sure, any size the chip supports (up to 2048x1536) and your host can handle. > Is it possible to configure the driver to stream at a > specific fps? No, patches welcome. > We have a version of the driver used internally > and it can do capture and stream of Bayer RGB data at VGA, > 480p, 576p and 720p resolutions. I have started integrating > your driver with my vpfe capture driver and it wasn't very > clear to me. Looks like driver calculates the timing parameters > based on the width and height of the capture area. Yes, it provides exposure control by setting shutter timing, and it emulates autoexposure by calculating shutter times from window geometry. > We need > streaming capability in the driver. This is how our driver works > with mt9t031 sensor > raw-bus (10 bit) > vpfe-capture ----------------- mt9t031 driver > | | > V V > VPFE MT9T031 > > VPFE hardware has internal timing and DMA controller to > copy data frame by frame from the sensor output to SDRAM. > The PCLK form the sensor is used to generate the internal > timing. So, what is missing in the driver apart from the ability to specify a frame-rate? Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/ -- 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
