Hi, Em Fri, 17 Nov 2017 02:58:56 +0000 "Mani, Rajmohan" <rajmohan.mani@xxxxxxxxx> escreveu: > Here is an update on the IPU3 documentation that we are currently working on. > > Image processing in IPU3 relies on the following. > > 1) HW configuration to enable ISP and > 2) setting customer specific 3A Tuning / Algorithm Parameters to achieve desired image quality. > > We intend to provide documentation on ImgU driver programming interface to help users of this driver to configure and enable ISP HW to meet their needs. This documentation will include details on complete V4L2 Kernel driver interface and IO-Control parameters, except for the ISP internal algorithm and its parameters (which is Intel proprietary IP). Sakari asked me to take a look on this thread, specifically on this email. I took a look on the other e-mails from this thread that are discussing about this IP block. I understand that Intel wants to keep their internal 3A algorithm protected, just like other vendors protect their own algos. It was never a requirement to open whatever algorithm are used inside a hardware (or firmware). The only requirement is that firmwares should be licensed with redistribution permission, ideally merged at linux-firmware git tree. Yet, what I don't understand is why Intel also wants to also protect the interface for such 3A hardware/firmware algorithm. The parameters that are passed from an userspace application to Intel ISP logic doesn't contain the algorithm itself. What's the issue of documenting the meaning of each parameter? Thanks, Mauro
