From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 805AFE00C7B; Sun, 4 Oct 2015 23:50:15 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from dev.rtsoft.ru (mail.dev.rtsoft.ru [213.79.90.226]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id EDD92E007B3 for ; Sun, 4 Oct 2015 23:50:08 -0700 (PDT) Received: from [192.168.112.12] (fw-int.dev.rtsoft.ru [192.168.1.70]) by dev.rtsoft.ru (Postfix) with ESMTP id 8B38F438FA; Mon, 5 Oct 2015 09:50:01 +0300 (MSK) Message-ID: <56121D99.10908@dev.rtsoft.ru> Date: Mon, 05 Oct 2015 09:50:01 +0300 From: Nikita Yushchenko Organization: RTSoft Software Development Center User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 MIME-Version: 1.0 To: "Dmitriy B." References: <560AF019.5060700@dev.rtsoft.ru> In-Reply-To: Cc: Gennady Kuznetsov , "meta-freescale@yoctoproject.org" , arusalin Subject: Re: OV5640 autofocus kernel+gstreamer+Qt implementation X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Oct 2015 06:50:15 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi Dmitry. Sorry missed your mail (I'm not at list) >> Kernel patches are against imx_3.14.28_1.0.0_ga branch. >> >> First patch is generic mxc_v4l2_capture cleanup. Unfortunately driver >> was quite racy and did not survive even streaming stop+start from within >> Qt. Had to do some cleanup to mitigate that. >> >> Second patch contains actual implementation of focus-related v4l ioctls. >> >> Autofocus firmware embedded into patch was taken from >> http://crewrktablets.arctablet.com:8080/opendev/kernel_rockchip.git, >> branch rockchip-3.10-rk3288 >> file drivers/media/video/ov5640_af_firmware.c >> and converted to format that existing driver uses. I've tried different >> firmwares found over the net, this one shows the best behaviour. >> > > Interesting, you seem to have better implementation of AF than > https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.10.53_1.1.1_ga/drivers/media/platform/mxc/capture/ov5640_mipi.c#L120 I've seen that, but it is incomplete, single AF only, no notifications, etc. My implementation does not have manual adjustment ... but I do not like idea to use custom command for that, V4L has V4L2_CID_FOCUS_ABSOLUTE / V4L2_CID_FOCUS_RELATIVE for that. Also, I did the full stack - from Qt through gstreamer to kernel. This is what I believe is not yet available in opensource ... at least I was not able find any GstPhotography implementation in the net, just mentions that it was used in Maemo and probably is used in some closed projects. >> *) Legal status of AF firmware is unclear. >> > > Boundarydevices and Arrow (Wandcam) distribute the above mentioned source > of AF firmware for long time now. > Should not be a problem, since they already licensed it. Another question > is if you changed it or distribute unknown Chinese unlicensed manufacturer > firmware. Firmware version that I got from crewrktablets kernel_rockchip repo has working continuous AF. BoundaryDevices version does not. Internally, we are working with OmniVision to get official supported firmware - but that will likely be under NDA and thus I won't be able to share it. By re-distributing firmware from crewrktablets repo, I just publish what is already available. >> *) Setting camera parameters is not implemented. Camera always captures >> at 640x480 with all default settings. > > boundarydevices implemented that > https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.10.53_1.1.1_ga/drivers/media/platform/mxc/capture/ov5640_mipi.c#L56 Thanks for the link, will check. >> *) 'imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_5 = 0x00000001' >> message sometimes appears >> > > Carlos might know? I remember seeing something like this when using gst-imx. Any hint here will be useful... > > >> Any comments on all this are welcome. >> >> Nikita Yushchenko, >> System Software Engineer at Software Development Center, RTsoft > > > BR, > Dmitriy Beykun > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: >