Hi Manjunath, On Monday 04 July 2011 07:58:06 Hadli, Manjunath wrote: > On Thu, Jun 30, 2011 at 19:27:36, Sakari Ailus wrote: [snip] > > I understand that not all the blocks are there. Are there any major > > functional differences between those in Davinci and those in OMAP 3? > > Could the OMAP 3 ISP driver made support Davinci ISP as well? > > Yes, there are a lot of major differences between OMAP3 and Dm365/Dm355, > both in terms of features, there IP, and the software interface, including > all the registers which are entirely different. The closest omap3 would > come to is only to DM6446. I do not think OMAP3 driver can be made to > support Dm355 and Dm365. It is good to keep the OMAP3 neat and clean to > cater for OMAP4 and beyond, and keep the Davinci family separate. The > names might look similar and hence confusing for you, but the names can as > well be made the same as Dm365 blocks like ISIF and IPIPE and IPIPEIF > which are different. The DM6446 ISP is very similar to the OMAP3 ISP, and thus quite different from the DM355/365 ISPs. Should the DM6446 be supported by the OMAP3 ISP driver, and the DM355/365 by this driver ? > > There are number of possible improvements that still should be made to > > the OMAP 3 ISP driver so this way both of the driver would easily get > > them. To mention some: > > > > - Multiple output pipeline > > - Switch to videobuf2 > > - Switch to GENIRQ > > Sure. There is definitely a design element convergence, and overtime I > think some of these would get into the core v4l2 infrastructure. -- 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
