All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCHv2 1/9] v4l2-mediabus.h: add hsv_enc
Date: Mon, 16 Apr 2018 15:12:14 -0300	[thread overview]
Message-ID: <20180416151214.77b46351@vento.lan> (raw)
In-Reply-To: <20180416132121.46205-2-hverkuil@xs4all.nl>

Em Mon, 16 Apr 2018 15:21:13 +0200
Hans Verkuil <hverkuil@xs4all.nl> escreveu:

> From: Hans Verkuil <hans.verkuil@cisco.com>
> 
> Just like struct v4l2_pix_format add a hsv_enc field to describe
> the HSV encoding. It is in a union with the ycbcr_enc, since it
> is one or the other.
> 
> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
> ---
>  include/uapi/linux/v4l2-mediabus.h | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/include/uapi/linux/v4l2-mediabus.h b/include/uapi/linux/v4l2-mediabus.h
> index 123a231001a8..52fd6cc9d491 100644
> --- a/include/uapi/linux/v4l2-mediabus.h
> +++ b/include/uapi/linux/v4l2-mediabus.h
> @@ -24,6 +24,7 @@
>   * @field:	used interlacing type (from enum v4l2_field)
>   * @colorspace:	colorspace of the data (from enum v4l2_colorspace)
>   * @ycbcr_enc:	YCbCr encoding of the data (from enum v4l2_ycbcr_encoding)
> + * @hsv_enc:	HSV encoding of the data (from enum v4l2_hsv_encoding)
>   * @quantization: quantization of the data (from enum v4l2_quantization)
>   * @xfer_func:  transfer function of the data (from enum v4l2_xfer_func)
>   */
> @@ -33,7 +34,12 @@ struct v4l2_mbus_framefmt {
>  	__u32			code;
>  	__u32			field;
>  	__u32			colorspace;
> -	__u16			ycbcr_enc;
> +	union {
> +		/* enum v4l2_ycbcr_encoding */
> +		__u16		ycbcr_enc;
> +		/* enum v4l2_hsv_encoding */
> +		__u16		hsv_enc;
> +	};

While I'm OK with that, it currently doesn't make sense to apply
it, as no driver is currently using v4l2_mbus_framefmt.hsv_enc.

>  	__u16			quantization;
>  	__u16			xfer_func;
>  	__u16			reserved[11];



Thanks,
Mauro

  reply	other threads:[~2018-04-16 18:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 13:21 [PATCHv2 0/9] media/mc: fix inconsistencies Hans Verkuil
2018-04-16 13:21 ` [PATCHv2 1/9] v4l2-mediabus.h: add hsv_enc Hans Verkuil
2018-04-16 18:12   ` Mauro Carvalho Chehab [this message]
2018-04-16 13:21 ` [PATCHv2 2/9] subdev-formats.rst: fix incorrect types Hans Verkuil
2018-04-16 13:21 ` [PATCHv2 3/9] media.h: remove __NEED_MEDIA_LEGACY_API Hans Verkuil
2018-04-16 17:56   ` Mauro Carvalho Chehab
2018-04-16 13:21 ` [PATCHv2 4/9] media: add function field to struct media_entity_desc Hans Verkuil
2018-04-16 18:01   ` Mauro Carvalho Chehab
2018-04-16 19:27     ` Hans Verkuil
2018-04-16 19:40       ` Mauro Carvalho Chehab
2018-04-16 19:48         ` Hans Verkuil
2018-04-17 12:02           ` Mauro Carvalho Chehab
2018-04-16 13:21 ` [PATCHv2 5/9] media-ioc-enum-entities.rst: document new 'function' field Hans Verkuil
2018-04-16 18:02   ` Mauro Carvalho Chehab
2018-04-16 13:21 ` [PATCHv2 6/9] media: add 'index' to struct media_v2_pad Hans Verkuil
2018-04-16 18:03   ` Mauro Carvalho Chehab
2018-04-16 18:09     ` Mauro Carvalho Chehab
2018-04-16 19:41       ` Hans Verkuil
2018-04-17  9:59         ` Hans Verkuil
2018-04-17 11:55           ` Mauro Carvalho Chehab
2018-04-17 12:01             ` Hans Verkuil
2018-04-17 12:16               ` Mauro Carvalho Chehab
2018-04-17 12:19                 ` Hans Verkuil
2018-06-15 13:14                   ` Hans Verkuil
2018-04-16 13:21 ` [PATCHv2 7/9] media-ioc-g-topology.rst: document new 'index' field Hans Verkuil
2018-04-16 18:04   ` Mauro Carvalho Chehab
2018-04-16 13:21 ` [PATCHv2 8/9] media: add flags field to struct media_v2_entity Hans Verkuil
2018-04-16 13:21 ` [PATCHv2 9/9] media-ioc-g-topology.rst: document new 'flags' field Hans Verkuil
2018-04-16 18:10   ` Mauro Carvalho Chehab

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=20180416151214.77b46351@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=hans.verkuil@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.