public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Hans Verkuil <hansverk@cisco.com>
Subject: Re: [PATCH 1/5] media: replace ADOBERGB by OPRGB
Date: Thu, 13 Sep 2018 11:29:03 -0300	[thread overview]
Message-ID: <20180913112903.7275b126@coco.lan> (raw)
In-Reply-To: <20180913114731.16500-2-hverkuil@xs4all.nl>

Em Thu, 13 Sep 2018 13:47:27 +0200
Hans Verkuil <hverkuil@xs4all.nl> escreveu:

> From: Hans Verkuil <hansverk@cisco.com>
> 
> The CTA-861 standards have been updated to refer to opRGB instead
> of AdobeRGB. The official standard is in fact named opRGB, so
> switch to that.
> 
> The two old defines referring to ADOBERGB in the public API are
> put under #ifndef __KERNEL__ and a comment mentions that they are
> deprecated.
> 
> Signed-off-by: Hans Verkuil <hansverk@cisco.com>


> index 184e4dbe8f9c..c1e14a3b476e 100644
> --- a/include/uapi/linux/videodev2.h
> +++ b/include/uapi/linux/videodev2.h
> @@ -225,8 +225,12 @@ enum v4l2_colorspace {
>  	/* For RGB colorspaces such as produces by most webcams. */
>  	V4L2_COLORSPACE_SRGB          = 8,
>  
> -	/* AdobeRGB colorspace */
> +	/* opRGB colorspace */
> +	V4L2_COLORSPACE_OPRGB         = 9,
> +#ifndef __KERNEL__
> +	/* Deprecated alias for V4L2_COLORSPACE_OPRGB */
>  	V4L2_COLORSPACE_ADOBERGB      = 9,
> +#endif
>  
>  	/* BT.2020 colorspace, used for UHDTV. */
>  	V4L2_COLORSPACE_BT2020        = 10,
> @@ -258,7 +262,7 @@ enum v4l2_xfer_func {
>  	 *
>  	 * V4L2_COLORSPACE_SRGB, V4L2_COLORSPACE_JPEG: V4L2_XFER_FUNC_SRGB
>  	 *
> -	 * V4L2_COLORSPACE_ADOBERGB: V4L2_XFER_FUNC_ADOBERGB
> +	 * V4L2_COLORSPACE_OPRGB: V4L2_XFER_FUNC_OPRGB
>  	 *
>  	 * V4L2_COLORSPACE_SMPTE240M: V4L2_XFER_FUNC_SMPTE240M
>  	 *
> @@ -269,7 +273,11 @@ enum v4l2_xfer_func {
>  	V4L2_XFER_FUNC_DEFAULT     = 0,
>  	V4L2_XFER_FUNC_709         = 1,
>  	V4L2_XFER_FUNC_SRGB        = 2,
> +	V4L2_XFER_FUNC_OPRGB       = 3,
> +#ifndef __KERNEL__
> +	/* Deprecated alias for V4L2_XFER_FUNC_OPRGB */
>  	V4L2_XFER_FUNC_ADOBERGB    = 3,
> +#endif
>  	V4L2_XFER_FUNC_SMPTE240M   = 4,
>  	V4L2_XFER_FUNC_NONE        = 5,
>  	V4L2_XFER_FUNC_DCI_P3      = 6,

Nitpick: instead of having #ifndef inside the enum, I would instead
place both V4L2_COLORSPACE_ADOBERGB and V4L2_XFER_FUNC_ADOBERGB on
a separate #define, e. g:

/*
 * Deprecated names for Optional RGB colorspace (IEC 61966-2)
 *
 * WARNING: Please don't use it on your code, as those can be removed
 * from Kernelspace in the future.
 */
#ifndef __KERNEL__
# define V4L2_COLORSPACE_ADOBERGB V4L2_COLORSPACE_OPRGB
# define V4L2_XFER_FUNC_ADOBERGB  V4L2_XFER_FUNC_OPRGB
#endif

There are two reasons for that:

1) by adding them inside enums and not documenting, you may
   end by having warnings;

2) as you mentioned on patch 0/5, one of the goals is to
   "avoid possible future trademark complaints."

So, better to add a clear warning at the Kernel that we may need
to remove it in the future.

Thanks,
Mauro

  reply	other threads:[~2018-09-13 19:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13 11:47 [PATCH 0/5] Rename AdobeRGB to opRGB Hans Verkuil
2018-09-13 11:47 ` [PATCH 1/5] media: replace ADOBERGB by OPRGB Hans Verkuil
2018-09-13 14:29   ` Mauro Carvalho Chehab [this message]
2018-09-13 14:35     ` Hans Verkuil
2018-09-14  8:58   ` [PATCHv2 " Hans Verkuil
2018-09-13 11:47 ` [PATCH 2/5] media colorspaces*.rst: rename AdobeRGB to opRGB Hans Verkuil
2018-09-13 11:47 ` [PATCH 3/5] hdmi.h: rename ADOBE_RGB to OPRGB and ADOBE_YCC to OPYCC Hans Verkuil
2018-09-13 11:47 ` [PATCH 4/5] drm/bridge/synopsys/dw-hdmi.h: rename ADOBE to OP Hans Verkuil
2018-09-13 11:47 ` [PATCH 5/5] drm/amd: " Hans Verkuil
2018-09-13 13:46 ` [PATCH 0/5] Rename AdobeRGB to opRGB Daniel Vetter

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=20180913112903.7275b126@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hansverk@cisco.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    /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