Hello everyone,
I'm posting this RFC one more time because it seems to everyone has
been forgot this, and I'll be appreciated if any of you who is reading
this mailing list give me comment.
I'm adding some choices for you to make it easier. (even the option
for that this is a pointless discussion)
I've got a big question popping up handling white balance with
V4L2_CID_WHITE_BALANCE_TEMPERATURE CID.
Because in digital camera we generally control over user interface
with pre-defined white balance name. I mean, user controls white
balance with presets not with kelvin number.
I'm very certain that TEMPERATURE CID is needed in many of video
capture devices, but also 100% sure that white balance preset control
is also necessary for digital cameras.
How can we control white balance through preset name with existing V4L2 API?
For now, I define preset names in user space with supported color
temperature preset in driver like following.
#define MANUAL_WB_TUNGSTEN 3000
#define MANUAL_WB_FLUORESCENT 4000
#define MANUAL_WB_SUNNY 5500
#define MANUAL_WB_CLOUDY 6000
and make driver to handle those presets like this. (I split in several
ranges to make driver pretend to be generic)
case V4L2_CID_WHITE_BALANCE_TEMPERATURE:
if (vc->value < 3500) {
/* tungsten */
err = ce131f_cmds(c, ce131f_wb_tungsten);
} else if (vc->value < 4100) {
/* fluorescent */
err = ce131f_cmds(c, ce131f_wb_fluorescent);
} else if (vc->value < 6000) {
/* sunny */
err = ce131f_cmds(c, ce131f_wb_sunny);
} else if (vc->value < 6500) {
/* cloudy */
err = ce131f_cmds(c, ce131f_wb_cloudy);
} else {
printk(KERN_INFO "%s: unsupported kelvin
range\n", __func__);
}
......
I think this way seems to be ugly. Don't you think that another CID is
necessary to handle WB presets?
Because most of mobile camera modules can't make various color
temperatures in expecting kelvin number with user parameter.
So, here you are some options you can chose to give your opinion.(or
you can make your own opinion)
(A). Make a new CID to handle well known white balance presets
Like V4L2_CID_WHITE_BALANCE_PRESET for CID and enum values like
following for value
enum v4l2_whitebalance_presets {
V4L2_WHITEBALANCE_TUNGSTEN = 0,
V4L2_WHITEBALANCE_FLUORESCENT,
V4L2_WHITEBALANCE_SUNNY,
V4L2_WHITEBALANCE_CLOUDY,
....
(B). Define well known kelvin number in videodev2.h as preset name and
share with user space
Like following
#define V4L2_WHITEBALANCE_TUNGSTEN 3000
#define V4L2_WHITEBALANCE_FLUORESCENT 4000
#define V4L2_WHITEBALANCE_SUNNY 5500
#define V4L2_WHITEBALANCE_CLOUDY 6000
and use those defined values with V4L2_CID_WHITE_BALANCE_TEMPERATURE
urgh.....
(C). Leave it alone. It's a pointless discussion. we are good with
existing WB API.
(really?)
I'm very surprised about this kind of needs were not issued yet.
Any opinion will be appreciated.
Regards,
Nate
--
========================================================
DongSoo, Nathaniel Kim
Engineer
Mobile S/W Platform Lab.
Digital Media & Communications R&D Centre
Samsung Electronics CO., LTD.
e-mail : dongsoo....@gmail.com
dongsoo45....@samsung.com
========================================================
--
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
