From: Hans Verkuil <hverkuil@xs4all.nl>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: 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 <linux-media@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/6] [media] Documentation: Add HSV format
Date: Sat, 16 Jul 2016 17:28:08 +0200 [thread overview]
Message-ID: <94f0b9bc-542b-6e19-3ca1-332632c135f7@xs4all.nl> (raw)
In-Reply-To: <CAPybu_2N+gKU4=qRfxHhEurTvUqT0f8Pup55C8KKTT_jEwf2nw@mail.gmail.com>
On 07/16/2016 04:32 PM, Ricardo Ribalda Delgado wrote:
> Hi
>
> On Sat, Jul 16, 2016 at 4:12 PM, Laurent Pinchart
> <laurent.pinchart@ideasonboard.com> wrote:
>
>> I'd still like to know about it for my personal information :-)
>
> Maybe it is just a very cheap gamma.
>
>>
>>> Anyway, I am inclined to use ycbcr_enc as well.
>>
>> I'm glad we agree.
>>
>
> Are you thinking about something like this:
>
>
> diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
> index c7fb760386cf..3e613fba1b20 100644
> --- a/include/uapi/linux/videodev2.h
> +++ b/include/uapi/linux/videodev2.h
> @@ -330,6 +330,16 @@ enum v4l2_ycbcr_encoding {
> V4L2_YCBCR_ENC_SMPTE240M = 8,
> };
>
> +enum v4l2_hsv_encoding {
> + V4L2_HSV_ENC_180 = 16,
> + V4L2_HSV_ENC_256 = 17,
> +};
Yes.
> +
> +enum v4l2_rgb_encoding {
> + V4L2_RGB_ENC_FULL = 32,
> + V4L2_HSV_ENC_16_235 = 33,
> +};
No.
The starting point is RGB, so there is nothing to encode. YCbCr and HSV
are transformations from RGB (or R'G'B' to be precise).
The basic chain is:
XYZ -> colorspace conversion -> RGB -> transfer function -> R'G'B'
and after this there is an optional step that converts R'G'B' to
Y'CbCr or HSV (ycbcr_enc or hsv_enc). The final step is the quantization
step where you end up with the actual color component values.
There doesn't seem to be something like limited range HSV, so I'd say it's
full range only.
Regards,
Hans
> +
> /*
> * Determine how YCBCR_ENC_DEFAULT should map to a proper Y'CbCr encoding.
> * This depends on the colorspace.
> @@ -455,7 +465,11 @@ struct v4l2_pix_format {
> __u32 colorspace; /* enum v4l2_colorspace */
> __u32 priv; /* private data,
> depends on pixelformat */
> __u32 flags; /* format flags
> (V4L2_PIX_FMT_FLAG_*) */
> - __u32 ycbcr_enc; /* enum v4l2_ycbcr_encoding */
> + union {
> + __u32 ycbcr_enc; /* enum
> v4l2_ycbcr_encoding */
> + __u32 hsv_enc; /* enum
> v4l2_hsv_encoding */
> + __u32 rgb_enc; /* enum
> v4l2_rgb_encoding */
> + };
> __u32 quantization; /* enum v4l2_quantization */
> __u32 xfer_func; /* enum v4l2_xfer_func */
> };
> @@ -1988,7 +2002,11 @@ struct v4l2_pix_format_mplane {
> struct v4l2_plane_pix_format plane_fmt[VIDEO_MAX_PLANES];
> __u8 num_planes;
> __u8 flags;
> - __u8 ycbcr_enc;
> + union {
> + __u8 ycbcr_enc; /* enum
> v4l2_ycbcr_encoding */
> + __u8 hsv_enc; /* enum
> v4l2_hsv_encoding */
> + __u8 rgb_enc; /* enum
> v4l2_rgb_encoding */
> + };
> __u8 quantization;
> __u8 xfer_func;
> __u8 reserved[7];
>
>> --
>
>
> Best regards!
>
next prev parent reply other threads:[~2016-07-16 15:28 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 [this message]
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
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=94f0b9bc-542b-6e19-3ca1-332632c135f7@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=laurent.pinchart@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).