New Driver for DaVinci DM355/DM365/DM6446
Hello, WE have a module(H3A) on Davinci DM6446,DM355 and DM365. Customers require a way to collect the data required to perform the Auto Exposure (AE), Auto Focus(AF), and Auto White balance (AWB) in hardware as opposed to software. This is primarily for performance reasons as there is not enough software processing MIPS (to do 3A statistics) available in an imaging/video system. Including this block in hardware reduces the load on the processor and bandwidth to the memory as the data is collected on the fly from the imager. This modules collects statistics and we currently implement it as a character driver. Which mailing list would be the most appropriate mailing list to submit patches for review? Thanks, Sandeep -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: New Driver for DaVinci DM355/DM365/DM6446
-Original Message- From: Mauro Carvalho Chehab [mailto:mche...@infradead.org] Sent: Monday, June 01, 2009 12:35 PM To: Paulraj, Sandeep Cc: linux-media@vger.kernel.org; linux-ker...@vger.kernel.org; Grosen, Mark Subject: Re: New Driver for DaVinci DM355/DM365/DM6446 Em Mon, 1 Jun 2009 09:56:40 -0500 Paulraj, Sandeep s-paul...@ti.com escreveu: Hello, WE have a module(H3A) on Davinci DM6446,DM355 and DM365. Customers require a way to collect the data required to perform the Auto Exposure (AE), Auto Focus(AF), and Auto White balance (AWB) in hardware as opposed to software. This is primarily for performance reasons as there is not enough software processing MIPS (to do 3A statistics) available in an imaging/video system. Including this block in hardware reduces the load on the processor and bandwidth to the memory as the data is collected on the fly from the imager. This modules collects statistics and we currently implement it as a character driver. Which mailing list would be the most appropriate mailing list to submit patches for review? You should send they to: LMML linux-media@vger.kernel.org If you are proposing API changes, please submit they first. [Sandeep] WE don't propose any API changes. This module for which we want to submit patches is a TI proprietary IP. We currently implement this as a character device and have a few IOCTL's. We do not follow the V4L2 framework and do not use any V4L2 IOCTLs. Can we continue to use it as a character driver? Thanks, Sandeep -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Cheers, Mauro -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: New Driver for DaVinci DM355/DM365/DM6446
Mauro, Please see inline -Original Message- From: Mauro Carvalho Chehab [mailto:mche...@infradead.org] Sent: Monday, June 01, 2009 1:57 PM To: Paulraj, Sandeep Cc: linux-media@vger.kernel.org; linux-ker...@vger.kernel.org; Grosen, Mark Subject: Re: New Driver for DaVinci DM355/DM365/DM6446 Em Mon, 1 Jun 2009 11:54:37 -0500 Paulraj, Sandeep s-paul...@ti.com escreveu: -Original Message- From: Mauro Carvalho Chehab [mailto:mche...@infradead.org] Sent: Monday, June 01, 2009 12:35 PM To: Paulraj, Sandeep Cc: linux-media@vger.kernel.org; linux-ker...@vger.kernel.org; Grosen, Mark Subject: Re: New Driver for DaVinci DM355/DM365/DM6446 Em Mon, 1 Jun 2009 09:56:40 -0500 Paulraj, Sandeep s-paul...@ti.com escreveu: Hello, WE have a module(H3A) on Davinci DM6446,DM355 and DM365. Customers require a way to collect the data required to perform the Auto Exposure (AE), Auto Focus(AF), and Auto White balance (AWB) in hardware as opposed to software. This is primarily for performance reasons as there is not enough software processing MIPS (to do 3A statistics) available in an imaging/video system. Including this block in hardware reduces the load on the processor and bandwidth to the memory as the data is collected on the fly from the imager. This modules collects statistics and we currently implement it as a character driver. Which mailing list would be the most appropriate mailing list to submit patches for review? You should send they to: LMML linux-media@vger.kernel.org If you are proposing API changes, please submit they first. [Sandeep] WE don't propose any API changes. This module for which we want to submit patches is a TI proprietary IP. We currently implement this as a character device and have a few IOCTL's. We do not follow the V4L2 framework and do not use any V4L2 IOCTLs. Can we continue to use it as a character driver? In this case, I don't see why you want it to be upstream. [Sandeep] TI customers and TI itself want to see this driver part of open source trees. Considering this we would like to submit our patches to the linux-media mailing list. IS this OK? Cheers, Mauro -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
