From: Hans Verkuil <hverkuil@xs4all.nl>
To: Jean-Marc VOLLE <jean-marc.volle@st.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Cc: Divneil Rai WADHAWAN <divneil.wadhawan@st.com>
Subject: Re: [PATCH] ITU BT2020 support in v4l2_colorspace
Date: Fri, 01 Aug 2014 17:09:49 +0200 [thread overview]
Message-ID: <53DBADBD.7060407@xs4all.nl> (raw)
In-Reply-To: <1406905371-17609-1-git-send-email-jean-marc.volle@st.com>
On 08/01/2014 05:02 PM, Jean-Marc VOLLE wrote:
> From: vollejm <jean-marc.volle@st.com>
>
> UHD video content may be encoded using a new color space (BT2020). This patch
> adds it to the v4l2_colorspace enum
I'm not opposed to this, but have you actually seen video streams with this
colorspace?
More to the point, this colorspace is only valid for 10 and 12 bit deep colors
(something that should be documented as well), and I don't think we even have PIX_FMT
defines for that. Are there plans to add support for that?
Regards,
Hans
>
>
> Signed-off-by: <jean-marc.volle@st.com>
> ---
> Documentation/DocBook/media/v4l/biblio.xml | 10 ++++++++++
> Documentation/DocBook/media/v4l/pixfmt.xml | 14 ++++++++++++++
> include/uapi/linux/videodev2.h | 4 ++++
> 3 files changed, 28 insertions(+)
>
> diff --git a/Documentation/DocBook/media/v4l/biblio.xml b/Documentation/DocBook/media/v4l/biblio.xml
> index d2eb79e..d3930cf 100644
> --- a/Documentation/DocBook/media/v4l/biblio.xml
> +++ b/Documentation/DocBook/media/v4l/biblio.xml
> @@ -117,6 +117,16 @@ url="http://www.itu.ch">http://www.itu.ch</ulink>)</corpauthor>
> <title>ITU-R Recommendation BT.1119 "625-line
> television Wide Screen Signalling (WSS)"</title>
> </biblioentry>
> + <biblioentry id="itu2020">
> + <abbrev>ITU BT.2020</abbrev>
> + <authorgroup>
> + <corpauthor>International Telecommunication Union (<ulink
> +url="http://www.itu.ch">http://www.itu.ch</ulink>)</corpauthor>
> + </authorgroup>
> + <title>ITU-R Recommendation BT.2020 "Parameter values for
> + ultra-high definition television systems for production
> + and international programme exchange"</title>
> + </biblioentry>
>
> <biblioentry id="jfif">
> <abbrev>JFIF</abbrev>
> diff --git a/Documentation/DocBook/media/v4l/pixfmt.xml b/Documentation/DocBook/media/v4l/pixfmt.xml
> index 91dcbc8..f0c70dd 100644
> --- a/Documentation/DocBook/media/v4l/pixfmt.xml
> +++ b/Documentation/DocBook/media/v4l/pixfmt.xml
> @@ -599,6 +599,20 @@ are still clamped to [0;255].</para>
> 1.099 I<superscript>0.45</superscript> - 0.099 for 0.018 < I</entry>
> <entry spanname="spam">n/a</entry>
> </row>
> + <row>
> + <entry><constant>V4L2_COLORSPACE_BT2020</constant></entry>
> + <entry>9</entry>
> + <entry>BT2020, see <xref linkend="itu2020" /></entry>
> + <entry>x = 0.708, y = 0.292</entry>
> + <entry>x = 0.170, y = 0.797</entry>
> + <entry>x = 0.131, y = 0.046</entry>
> + <entry>x = 0.3127, y = 0.3290,
> + Illuminant D<subscript>65</subscript></entry>
> + <entry>see <xref linkend="itu2020" /></entry>
> + <entry>see <xref linkend="itu2020" /></entry>
> + <entry>see <xref linkend="itu2020" /></entry>
> + <entry>see <xref linkend="itu2020" /></entry>
> + </row>
> </tbody>
> </tgroup>
> </table>
> diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
> index 168ff50..6af06e1 100644
> --- a/include/uapi/linux/videodev2.h
> +++ b/include/uapi/linux/videodev2.h
> @@ -197,6 +197,10 @@ enum v4l2_colorspace {
>
> /* For RGB colourspaces, this is probably a good start. */
> V4L2_COLORSPACE_SRGB = 8,
> +
> + /* UHD BT2020 colorspace */
> + V4L2_COLORSPACE_BT2020 = 9,
> +
> };
>
> enum v4l2_priority {
>
next prev parent reply other threads:[~2014-08-01 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 15:02 [PATCH] ITU BT2020 support in v4l2_colorspace Jean-Marc VOLLE
2014-08-01 15:09 ` Hans Verkuil [this message]
2014-08-01 15:54 ` Jean-Marc VOLLE
2014-08-01 16:36 ` Hans Verkuil
2014-08-04 8:49 ` Jean-Marc VOLLE
2014-08-04 9:13 ` Hans Verkuil
2014-11-17 14:37 ` Hans Verkuil
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=53DBADBD.7060407@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=divneil.wadhawan@st.com \
--cc=jean-marc.volle@st.com \
--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.