Hi Prabhakar, On Fri, Nov 16, 2012 at 08:15:02PM +0530, Prabhakar Lad wrote: > From: Manjunath Hadli <manjunath.hadli@xxxxxx> > > This patch set adds media controller based capture driver for > DM365. > > This driver bases its design on Laurent Pinchart's Media Controller Design > whose patches for Media Controller and subdev enhancements form the base. > The driver also takes copious elements taken from Laurent Pinchart and > others' OMAP ISP driver based on Media Controller. So thank you all the > people who are responsible for the Media Controller and the OMAP ISP driver. > > Also, the core functionality of the driver comes from the arago vpfe capture > driver of which the isif capture was based on V4L2, with other drivers like > ipipe, ipipeif and Resizer. > > Changes for v2: > 1: Migrated the driver for videobuf2 usage pointed Hans. > 2: Changed the design as pointed by Laurent, Exposed one more subdevs > ipipeif and split the resizer subdev into three subdevs. > 3: Rearrganed the patch sequence and changed the commit messages. > 4: Changed the file architecture as pointed by Laurent. > > Manjunath Hadli (12): > davinci: vpfe: add v4l2 capture driver with media interface > davinci: vpfe: add v4l2 video driver support > davinci: vpfe: dm365: add IPIPEIF driver based on media framework > davinci: vpfe: dm365: add ISIF driver based on media framework > davinci: vpfe: dm365: add IPIPE support for media controller driver > davinci: vpfe: dm365: add IPIPE hardware layer support > davinci: vpfe: dm365: resizer driver based on media framework > davinci: vpss: dm365: enable ISP registers > davinci: vpss: dm365: set vpss clk ctrl > davinci: vpss: dm365: add vpss helper functions to be used in the > main driver for setting hardware parameters > davinci: vpfe: dm365: add build infrastructure for capture driver > davinci: vpfe: Add documentation Many thanks for taking the driver this far! However, I feel that there's still some work to do, especially in the user space API. Some things could be implemented using the generic API but currently use davinci-specific API; private IOCTL is being used where controls would do, and resizing is enabled or disable explicitly in ipipeif configuration. Also, there are things such as internal clock frequencies visible in the API. I can go to more details soon after taking a closer look at the patches. If you wish to get this to mainline kernel fast, a viable option IMO would be the staging tree. What do you think? Cc Hans and Laurent. -- Kind regards, Sakari Ailus e-mail: sakari.ailus@xxxxxx XMPP: sailus@xxxxxxxxxxxxxx -- 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
