From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: "Wang, Wen W" <wen.w.wang@intel.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"Zhang, Xiaolin" <xiaolin.zhang@intel.com>,
"Hu, Gang A" <gang.a.hu@intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: Proposal to extend V4L2 Control ID for advanced imaging processing features.
Date: Tue, 12 Oct 2010 20:56:56 +0300 [thread overview]
Message-ID: <4CB4A168.2060105@maxwell.research.nokia.com> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A2A658B6D@shsmsx501.ccr.corp.intel.com>
Wang, Wen W wrote:
> Hi all,
Hi Wang,
Thanks for the proposal!
(Cc'ing Hans Verkuil.)
> We are developing a V4L2 device driver which the ISP has many
> advanced features such as manual exposure setting, GDC (Geometric
> Distortion Correction), CAC (Chromatic Aberration Correction), video
> stabilization, false color correction, shading correction, etc. But
> to control those features, we find current v4l2 framework has limited
> CIDs and cannot support these advanced features in normal way .
Manual exposure sounds like a sensor property, not ISP's. Are the rest
implemented in the ISP or is there a user space library to support them?
I think in either case the definition will be in kernel headers.
These controls appear quite high level to me. What about the specific
parameters for the functionality, I suppose shading correction for
example has a lot more parameters than just disable/enable?
> So we propose to extend the V4L2 CIDs and add the below CIDs. Can you
> please review and feel free to give your comments?
>
> V4L2_CID_ISO_ABSOLUTE -- This CID is used to set up manual ISO speed
> value. This CID has integer type and with as valid range or limited
> valid value, depending on the hardware. If the target value is not
> supported by hardware, a closest value will be set
> V4L2_CID_APERTURE_ABSOLUTE -- This CID is used to set up manual
> aperture value. This CID has integer type and with as valid range or
> limited valid value, depending on the hardware. If the target value
> is not supported by hardware, a closest value will be set
The above look like image sensor properties.
I wonder if it would make sense to create a new control class for these.
> V4L2_CID_ATOMISP_FIXED_PATTERN_NR - This CID is used to
> enable/disable Fixed pattern noise reduction. This CID has Boolean
> type and 0 indicate to disable fixed pattern NR and 1 indicate to
> enable it. V4L2_CID_ATOMISP_POSTPROCESS_XNR - This CID is used to
> enable/disable XNR. This CID has Boolean type and 0 indicate to
> disable XNR and 1 indicate to enable it.
> V4L2_CID_ATOMISP_POSTPROCESS_GDC_CAC - Our ISP combined GDC and CAC
> together. This CID is used to enable/disable GDC and CAC. This CID
> has Boolean type and 0 indicate to disable it and 1 indicate to
What are GDC and CAC?
> enable it. V4L2_CID_ATOMISP_VIDEO_STABILIZATION -- This CID is used
> to enable/disable video stabilization capability. This CID has
> Boolean type and 0 indicate to disable it and 1 indicate to enable
> it. V4L2_CID_ATOMISP_FALSE_COLOR_CORRECTION - This CID is used to
> enable color correction capability. This CID has Boolean type and 0
> indicate to disable it and 1 indicate to enable it.
Ps. Could you wrap your lines to 80 characters, please? That makes your
messages easier to read and reply. Thank you.
Regards,
--
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com
prev parent reply other threads:[~2010-10-12 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 10:40 Proposal to extend V4L2 Control ID for advanced imaging processing features Wang, Wen W
2010-10-12 17:56 ` Sakari Ailus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CB4A168.2060105@maxwell.research.nokia.com \
--to=sakari.ailus@maxwell.research.nokia.com \
--cc=gang.a.hu@intel.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=wen.w.wang@intel.com \
--cc=xiaolin.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox