From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Prabhakar Lad <prabhakar.csengg@gmail.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Sakari Ailus <sakari.ailus@iki.fi>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
dlos <davinci-linux-open-source@linux.davincidsp.com>,
linux-media <linux-media@vger.kernel.org>,
Prabhakar Lad <prabhakar.lad@ti.com>,
Manjunath Hadli <manjunath.hadli@ti.com>
Subject: Re: Gain controls in v4l2-ctrl framework
Date: Mon, 24 Sep 2012 13:00:34 +0200 [thread overview]
Message-ID: <1440297.PvW0ZMD1YU@avalon> (raw)
In-Reply-To: <50603C39.9060105@redhat.com>
Hi Hans,
On Monday 24 September 2012 12:55:53 Hans de Goede wrote:
> On 09/23/2012 01:26 PM, Prabhakar Lad wrote:
> > Hi All,
> >
> > The CCD/Sensors have the capability to adjust the R/ye, Gr/Cy, Gb/G,
> > B/Mg gain values.
> > Since these control can be re-usable I am planning to add the
> > following gain controls as part of the framework:
> >
> > 1: V4L2_CID_GAIN_RED
> > 2: V4L2_CID_GAIN_GREEN_RED
> > 3: V4L2_CID_GAIN_GREEN_BLUE
>
> Not all sensors have separate V4L2_CID_GAIN_GREEN_RED /
> V4L2_CID_GAIN_GREEN_BLUE, so we will need a separate control for sensors
> which have one combined gain called simply V4L2_CID_GAIN_GREEN
>
> Also do we really need separate V4L2_CID_GAIN_GREEN_RED /
> V4L2_CID_GAIN_GREEN_BLUE controls? I know hardware has them, but in my
> experience that is only done as it is simpler to make the hardware this way
> (fully symmetric sensor grid), have you ever tried actually using different
> gain settings for the 2 different green rows ?
>
> I've and that always results in an ugly checker board pattern. So I think we
> can and should only have a V4L2_CID_GAIN_GREEN, and for sensors with 2
> green gains have that control both, forcing both to always have the same
> setting, which is really what you want anyways ...
I've never had to set different gains for the two green components either,
although I haven't done much with them.
> > 4: V4L2_CID_GAIN_BLUE
> > 5: V4L2_CID_GAIN_OFFSET
>
> GAIN_OFFSET that sounds a bit weird... GAIN_OFFSET sounds like it is
> a number which gets added to the 3/4 gain settings before the gain gets
> applied, but I assume that you just mean a number which gets added to the
> value from the pixel, either before or after the gain is applied and I must
> admit I cannot come up with a better name.
>
> I believe (not sure) that some sensors have these per color ...
Some might at least.
> The question is if it makes sense to actually control this per color though,
> I don't think it does as it is meant to compensate for any fixed measuring
> errors, which are the same for all 3/4 colors.
The offset is usually applied after the gain, so you might need different
offsets to compensate for a fixed error that is multiplied by different gains.
> Note that all the sensor cells are exactly the same, later on a color grid
> gets added on top of the sensors to turn them into r/g/b cells, but
> physically they are the same cells, so with the same process and temperature
> caused measuring errors...
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2012-09-24 10:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 11:26 Gain controls in v4l2-ctrl framework Prabhakar Lad
2012-09-23 13:20 ` Sakari Ailus
2012-09-23 16:17 ` Laurent Pinchart
2012-09-23 16:27 ` Sakari Ailus
2012-09-24 11:05 ` Laurent Pinchart
2012-09-24 10:55 ` Hans de Goede
2012-09-24 11:00 ` Laurent Pinchart [this message]
2012-09-24 11:04 ` Hans de Goede
2012-09-24 14:42 ` Prabhakar Lad
2012-09-24 17:17 ` Chris MacGregor
2012-09-24 18:46 ` Hans de Goede
2012-09-24 19:16 ` Chris MacGregor
2012-09-24 20:12 ` Sakari Ailus
2012-09-24 20:27 ` Laurent Pinchart
2012-09-24 20:06 ` Sakari Ailus
2012-09-24 20:42 ` Laurent Pinchart
2012-09-26 6:44 ` Prabhakar Lad
2012-09-26 6:53 ` Chris MacGregor
2012-09-26 7:01 ` Prabhakar Lad
2012-09-26 7:42 ` Sakari Ailus
2012-09-26 7:46 ` Prabhakar Lad
2012-09-26 7:54 ` Sakari Ailus
2012-09-26 8:06 ` Prabhakar Lad
2012-09-26 14:42 ` Chris MacGregor
2012-09-26 15:23 ` Laurent Pinchart
2012-09-26 19:23 ` Sakari Ailus
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=1440297.PvW0ZMD1YU@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=g.liakhovetski@gmx.de \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=manjunath.hadli@ti.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.lad@ti.com \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@iki.fi \
/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