From: Hans Verkuil <hverkuil@xs4all.nl>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Antti Palosaari <crope@iki.fi>,
Guennadi Liakhovetski <guennadi.liakhovetski@intel.com>,
Helen Mae Koike Fornazier <helen.koike@collabora.co.uk>,
Philipp Zabel <p.zabel@pengutronix.de>,
Shuah Khan <shuahkh@osg.samsung.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/6] [media] vivid: Add support for HSV formats
Date: Fri, 15 Jul 2016 20:29:13 +0200 [thread overview]
Message-ID: <25a3d29f-b8cb-f7ff-91a7-9b9290d76bfb@xs4all.nl> (raw)
In-Reply-To: <1468599199-5902-6-git-send-email-ricardo.ribalda@gmail.com>
On 07/15/2016 06:13 PM, Ricardo Ribalda Delgado wrote:
> This patch adds support for V4L2_PIX_FMT_HSV24 and V4L2_PIX_FMT_HSV32.
>
> Signed-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
> ---
> drivers/media/common/v4l2-tpg/v4l2-tpg-core.c | 94 +++++++++++++++++++++++--
> drivers/media/platform/vivid/vivid-vid-common.c | 14 ++++
> include/media/v4l2-tpg.h | 1 +
> 3 files changed, 105 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/media/common/v4l2-tpg/v4l2-tpg-core.c b/drivers/media/common/v4l2-tpg/v4l2-tpg-core.c
> index acf0e6854832..85b9c1925dd9 100644
> --- a/drivers/media/common/v4l2-tpg/v4l2-tpg-core.c
> +++ b/drivers/media/common/v4l2-tpg/v4l2-tpg-core.c
> @@ -318,6 +318,10 @@ bool tpg_s_fourcc(struct tpg_data *tpg, u32 fourcc)
> tpg->hmask[0] = ~1;
> tpg->color_representation = TGP_COLOR_REPRESENTATION_YUV;
> break;
> + case V4L2_PIX_FMT_HSV24:
> + case V4L2_PIX_FMT_HSV32:
> + tpg->color_representation = TGP_COLOR_REPRESENTATION_HSV;
> + break;
> default:
> return false;
> }
> @@ -351,6 +355,7 @@ bool tpg_s_fourcc(struct tpg_data *tpg, u32 fourcc)
> break;
> case V4L2_PIX_FMT_RGB24:
> case V4L2_PIX_FMT_BGR24:
> + case V4L2_PIX_FMT_HSV24:
> tpg->twopixelsize[0] = 2 * 3;
> break;
> case V4L2_PIX_FMT_BGR666:
> @@ -361,6 +366,7 @@ bool tpg_s_fourcc(struct tpg_data *tpg, u32 fourcc)
> case V4L2_PIX_FMT_ARGB32:
> case V4L2_PIX_FMT_ABGR32:
> case V4L2_PIX_FMT_YUV32:
> + case V4L2_PIX_FMT_HSV32:
> tpg->twopixelsize[0] = 2 * 4;
> break;
> case V4L2_PIX_FMT_NV12:
> @@ -408,6 +414,7 @@ bool tpg_s_fourcc(struct tpg_data *tpg, u32 fourcc)
> tpg->twopixelsize[1] = 4;
> break;
> }
> +
> return true;
> }
> EXPORT_SYMBOL_GPL(tpg_s_fourcc);
> @@ -490,6 +497,64 @@ static inline int linear_to_rec709(int v)
> return tpg_linear_to_rec709[v];
> }
>
> +static void color_to_hsv(struct tpg_data *tpg, int r, int g, int b,
> + int *h, int *s, int *v)
> +{
> + int max_rgb, min_rgb, diff_rgb;
> + int aux;
> + int third;
> +
> + r >>= 4;
> + g >>= 4;
> + b >>= 4;
> +
> + /*V*/
Please add a space after /* and before */.
I also think it is better to write Value, Saturation, Hue instead of
V, S, H.
> + max_rgb = max3(r, g, b);
> + *v = max_rgb;
> + if (!max_rgb) {
> + *h = 0;
> + *s = 0;
> + return;
> + }
> +
> + /*S*/
> + min_rgb = min3(r, g, b);
> + diff_rgb = max_rgb - min_rgb;
> + aux = 255 * diff_rgb;
> + aux += max_rgb / 2;
> + aux /= max_rgb;
> + *s = aux;
> + if (!aux) {
> + *h = 0;
> + return;
> + }
> +
> + /*H*/
> + if (max_rgb == r) {
> + aux = g - b;
> + third = 0;
> + } else if (max_rgb == g) {
> + aux = b - r;
> + third = 60;
> + } else {
> + aux = r - g;
> + third = 120;
> + }
> +
> + aux *= 30;
> + aux += diff_rgb / 2;
> + aux /= diff_rgb;
> + aux += third;
> +
> + /*Clamp H*/
> + if (aux < 0)
> + aux += 180;
> + else if (aux > 180)
> + aux -= 180;
> + *h = aux;
> +
> +}
> +
> static void rgb2ycbcr(const int m[3][3], int r, int g, int b,
> int y_offset, int *y, int *cb, int *cr)
> {
> @@ -829,7 +894,19 @@ static void precalculate_color(struct tpg_data *tpg, int k)
> ycbcr_to_color(tpg, y, cb, cr, &r, &g, &b);
> }
>
> - if (tpg->color_representation == TGP_COLOR_REPRESENTATION_YUV) {
> + switch (tpg->color_representation) {
> + case TGP_COLOR_REPRESENTATION_HSV:
> + {
> + int h, s, v;
> +
> + color_to_hsv(tpg, r, g, b, &h, &s, &v);
> + tpg->colors[k][0] = h;
> + tpg->colors[k][1] = s;
> + tpg->colors[k][2] = v;
Would quantization (limited/full range) be relevant here? I don't know if limited
range would make sense (or what those limits would be).
Regards,
Hans
next prev parent reply other threads:[~2016-07-15 18:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 16:13 [PATCH v2 0/6] Add HSV format Ricardo Ribalda Delgado
2016-07-15 16:13 ` [PATCH v2 1/6] [media] videodev2.h Add HSV formats Ricardo Ribalda Delgado
2016-07-15 16:13 ` [PATCH v2 2/6] [media] Documentation: Add HSV format Ricardo Ribalda Delgado
2016-07-15 18:11 ` Laurent Pinchart
2016-07-16 8:19 ` Hans Verkuil
2016-07-16 12:38 ` Laurent Pinchart
2016-07-16 13:59 ` Hans Verkuil
2016-07-16 14:12 ` Laurent Pinchart
2016-07-16 14:32 ` Ricardo Ribalda Delgado
2016-07-16 15:28 ` Hans Verkuil
2016-07-16 15:57 ` Ricardo Ribalda Delgado
2016-07-16 16:14 ` Hans Verkuil
2016-07-16 15:19 ` Hans Verkuil
2016-07-16 8:22 ` Ricardo Ribalda Delgado
2016-07-15 16:13 ` [PATCH v2 3/6] [media] Documentation: Add Ricardo Ribalda Ricardo Ribalda Delgado
2016-07-15 16:13 ` [PATCH v2 4/6] [media] vivid: code refactor for color representation Ricardo Ribalda Delgado
2016-07-15 17:58 ` Hans Verkuil
2016-07-15 18:12 ` Hans Verkuil
2016-07-15 18:28 ` Hans Verkuil
2016-07-15 16:13 ` [PATCH v2 5/6] [media] vivid: Add support for HSV formats Ricardo Ribalda Delgado
2016-07-15 18:29 ` Hans Verkuil [this message]
2016-07-15 16:13 ` [PATCH v2 6/6] [media] vivid: Rename variable Ricardo Ribalda Delgado
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=25a3d29f-b8cb-f7ff-91a7-9b9290d76bfb@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=crope@iki.fi \
--cc=guennadi.liakhovetski@intel.com \
--cc=helen.koike@collabora.co.uk \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=p.zabel@pengutronix.de \
--cc=ricardo.ribalda@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=shuahkh@osg.samsung.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;
as well as URLs for NNTP newsgroup(s).