V4L2_CID_AUTO_FOCUS_START VS V4L2_CID_FOCUS_AUTO
Hi, Can anyone explain what is the difference between setting control V4L2_CID_FOCUS_AUTO to 1 and and issuing V4L2_CID_AUTO_FOCUS_START? Confused... -- Regards, Bin -- 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: V4l2 state transition
Nicolas, On 8 December 2014 at 22:31, Nicolas Dufresne nicolas.dufre...@collabora.com wrote: Le 2014-12-08 09:29, Nicolas Dufresne a écrit : Le 2014-12-08 00:19, Bin Chen a écrit : Can anyone comment is following state transition diagram for V4l2 user space program make sense? Do you see any issues if we were to enforce this constraint? I think you should request some buffers before streamon. If in capture, you should also queue the minimum amount of buffers. I forgot, setting input and format isn't strictly required. Driver should have decent default configured. Thanks for all the explaining. Nicolas -- Regards, Bin -- 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
V4l2 state transition
Hi, Can anyone comment is following state transition diagram for V4l2 user space program make sense? Do you see any issues if we were to enforce this constraint? Sorry for not being able to paste the ascii diagram correctly in gmail. So please check following link to view the diagram. http://pastebin.com/nZNh6uF0 Thanks. -- Regards, Bin -- 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: Add controls to query camera read only paramters
Hi Guennadi, On 10 November 2014 19:46, Guennadi Liakhovetski g.liakhovet...@gmx.de wrote: Hi Bin, On Sat, 8 Nov 2014, Bin Chen wrote: Hi Everyone, I need suggestions with regard to adding controls to query camera read only parameters (e.g maxZoom/maxExposureCompensation) as needed by Android Camera API[1]. I'm not sure all Android HAL metadata tags should be 1-to-1 implemented in V4L2. Yes, we won't need 1-1 mapping and I'm just trying to identify the gaps and will add only those that are make sense. Some of them can be derived from existing information, some are even more relevant to the HAL, then to the camera (kernel driver). We can do it in both places and the boundary is kind of blur, at least for me:). Any guideline to follow? Putting them in driver maybe reasonable in the sense that all hardware related information are put together in one place - the driver. V4L2_CID_PIXEL_RATE is an example in V4l2 to provide such read-only information. -- 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
Add controls to query camera read only paramters
Hi Everyone, I need suggestions with regard to adding controls to query camera read only parameters (e.g maxZoom/maxExposureCompensation) as needed by Android Camera API[1]. What is in my mind is to add a customized camera control ID for each parameter I want to query and return EACCES when being used wit VIDIOC_S_EXT_CTRLS. Or, I can port the compound controls [2] patch and then I only need to add one customized control ID. Comments? What is the better way to do this? [1] http://developer.android.com/reference/android/hardware/Camera.Parameters.html [2]http://comments.gmane.org/gmane.comp.video.linuxtv.scm/19545 -- Regards, Bin -- 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
