From: Hans Verkuil <hverkuil@xs4all.nl>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-media@vger.kernel.org, marbugge@cisco.com,
Thierry Reding <thierry.reding@avionic-design.de>,
Hans Verkuil <hans.verkuil@cisco.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] hdmi: add new HDMI 2.0 defines
Date: Mon, 01 Dec 2014 12:15:02 +0100 [thread overview]
Message-ID: <547C4DB6.9090300@xs4all.nl> (raw)
In-Reply-To: <20141201110321.GA11763@ulmo.nvidia.com>
On 12/01/2014 12:03 PM, Thierry Reding wrote:
> On Fri, Nov 28, 2014 at 03:50:49PM +0100, Hans Verkuil wrote:
>> From: Hans Verkuil <hans.verkuil@cisco.com>
>>
>> Add new Video InfoFrame colorspace information introduced in HDMI 2.0
>> and new Audio Coding Extension Types, also from HDMI 2.0.
>>
>> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
>> ---
>> include/linux/hdmi.h | 20 ++++++++++++++++++++
>> 1 file changed, 20 insertions(+)
>>
>> diff --git a/include/linux/hdmi.h b/include/linux/hdmi.h
>> index 11c0182..38fd2a0 100644
>> --- a/include/linux/hdmi.h
>> +++ b/include/linux/hdmi.h
>> @@ -37,6 +37,8 @@ enum hdmi_colorspace {
>> HDMI_COLORSPACE_RGB,
>> HDMI_COLORSPACE_YUV422,
>> HDMI_COLORSPACE_YUV444,
>> + HDMI_COLORSPACE_YUV420,
>> + HDMI_COLORSPACE_IDO_DEFINED = 7,
>> };
>>
>> enum hdmi_scan_mode {
>> @@ -77,6 +79,10 @@ enum hdmi_extended_colorimetry {
>> HDMI_EXTENDED_COLORIMETRY_S_YCC_601,
>> HDMI_EXTENDED_COLORIMETRY_ADOBE_YCC_601,
>> HDMI_EXTENDED_COLORIMETRY_ADOBE_RGB,
>> +
>> + /* The following EC values are only defined in CEA-861-F. */
>> + HDMI_EXTENDED_COLORIMETRY_BT2020_CONST_LUM,
>> + HDMI_EXTENDED_COLORIMETRY_BT2020,
>> };
>>
>> enum hdmi_quantization_range {
>> @@ -201,9 +207,23 @@ enum hdmi_audio_sample_frequency {
>>
>> enum hdmi_audio_coding_type_ext {
>> HDMI_AUDIO_CODING_TYPE_EXT_STREAM,
>> +
>> + /*
>> + * The next three CXT values are defined in CEA-861-E only.
>> + * They do not exist in older versions, and in CEA-861-F they are
>> + * defined as 'Not in use'.
>> + */
>> HDMI_AUDIO_CODING_TYPE_EXT_HE_AAC,
>> HDMI_AUDIO_CODING_TYPE_EXT_HE_AAC_V2,
>> HDMI_AUDIO_CODING_TYPE_EXT_MPEG_SURROUND,
>> +
>> + /* The following CXT values are only defined in CEA-861-F. */
>> + HDMI_AUDIO_CODING_TYPE_EXT_MPEG4_HE_AAC,
>> + HDMI_AUDIO_CODING_TYPE_EXT_MPEG4_HE_AAC_V2,
>> + HDMI_AUDIO_CODING_TYPE_EXT_MPEG4_AAC_LC,
>> + HDMI_AUDIO_CODING_TYPE_EXT_DRA,
>> + HDMI_AUDIO_CODING_TYPE_EXT_MPEG_HE_AAC_SURROUND,
>> + HDMI_AUDIO_CODING_TYPE_EXT_MPEG_AAC_LC_SURROUND = 10,
>
> I think the last two should be MPEG4_{HE_AAC,AAC}_SURROUND, and with
> that fixed:
>
> Reviewed-by: Thierry Reding <treding@nvidia.com>
>
You are correct, I will correct that.
Thanks,
Hans
next prev parent reply other threads:[~2014-12-01 11:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 14:50 [PATCH 0/3] hdmi: add unpack and logging functions Hans Verkuil
2014-11-28 14:50 ` [PATCH 1/3] hdmi: add new HDMI 2.0 defines Hans Verkuil
2014-12-01 11:03 ` Thierry Reding
2014-12-01 11:15 ` Hans Verkuil [this message]
2014-11-28 14:50 ` [PATCH 2/3] hdmi: added unpack and logging functions for InfoFrames Hans Verkuil
2014-12-01 13:15 ` Thierry Reding
2014-12-01 13:48 ` Hans Verkuil
2014-12-01 15:33 ` Thierry Reding
2014-12-01 15:41 ` Daniel Vetter
2014-11-28 14:50 ` [PATCH 3/3] adv7842: simplify InfoFrame logging 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=547C4DB6.9090300@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=dri-devel@lists.freedesktop.org \
--cc=hans.verkuil@cisco.com \
--cc=linux-media@vger.kernel.org \
--cc=marbugge@cisco.com \
--cc=thierry.reding@avionic-design.de \
--cc=thierry.reding@gmail.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