From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v5 4/9] video: Add generic HDMI infoframe helpers
Date: Fri, 22 Feb 2013 18:01:22 +0200 [thread overview]
Message-ID: <20130222160122.GP4469@intel.com> (raw)
In-Reply-To: <1361516611-2517-5-git-send-email-thierry.reding@avionic-design.de>
On Fri, Feb 22, 2013 at 08:03:26AM +0100, Thierry Reding wrote:
<snip>
> +enum hdmi_audio_coding_type {
> + HDMI_AUDIO_CODING_TYPE_STREAM,
> + HDMI_AUDIO_CODING_TYPE_PCM,
> + HDMI_AUDIO_CODING_TYPE_AC3,
> + HDMI_AUDIO_CODING_TYPE_MPEG1,
> + HDMI_AUDIO_CODING_TYPE_MP3,
> + HDMI_AUDIO_CODING_TYPE_MPEG2,
> + HDMI_AUDIO_CODING_TYPE_AAC_LC,
> + HDMI_AUDIO_CODING_TYPE_DTS,
> + HDMI_AUDIO_CODING_TYPE_ATRAC,
> + HDMI_AUDIO_CODING_TYPE_DSD,
> + HDMI_AUDIO_CODING_TYPE_EAC3,
> + HDMI_AUDIO_CODING_TYPE_DTS_HD,
> + HDMI_AUDIO_CODING_TYPE_MLP,
> + HDMI_AUDIO_CODING_TYPE_DST,
> + HDMI_AUDIO_CODING_TYPE_WMA_PRO,
+ HDMI_AUDIO_CODING_TYPE_EXT or something like it?
> +};
> +
> +enum hdmi_audio_sample_size {
> + HDMI_AUDIO_SAMPLE_SIZE_STREAM,
> + HDMI_AUDIO_SAMPLE_SIZE_16,
> + HDMI_AUDIO_SAMPLE_SIZE_20,
> + HDMI_AUDIO_SAMPLE_SIZE_24,
> +};
> +
> +enum hdmi_audio_sample_frequency {
> + HDMI_AUDIO_SAMPLE_FREQUENCY_STREAM,
> + HDMI_AUDIO_SAMPLE_FREQUENCY_32000,
> + HDMI_AUDIO_SAMPLE_FREQUENCY_44100,
> + HDMI_AUDIO_SAMPLE_FREQUENCY_48000,
> + HDMI_AUDIO_SAMPLE_FREQUENCY_88200,
> + HDMI_AUDIO_SAMPLE_FREQUENCY_96000,
> + HDMI_AUDIO_SAMPLE_FREQUENCY_176400,
> + HDMI_AUDIO_SAMPLE_FREQUENCY_192000,
> +};
> +
> +enum hdmi_audio_coding_type_ext {
> + HDMI_AUDIO_CODING_TYPE_EXT_STREAM,
The spec is a bit confusing w.r.t. this value, but I think this is
correct. Any other value is illegal when CT!=15, and when CT==15,
CXT=0 means that look at CT (infinite loop anyone?), or stream header.
Since the infinite loop option doesn't make sense, looking at the
stream header is the only option. Although I think it would be
generally safer to avoid that specific combination. I'm sure some
"clever" guy would actually implement the infinite loop instead.
> + HDMI_AUDIO_CODING_TYPE_EXT_HE_AAC,
> + HDMI_AUDIO_CODING_TYPE_EXT_HE_AAC_V2,
> + HDMI_AUDIO_CODING_TYPE_EXT_MPEG_SURROUND,
> +};
> +
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-02-22 16:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 7:03 [PATCH v5 0/9] Add HDMI infoframe helpers Thierry Reding
2013-02-22 7:03 ` [PATCH v5 1/9] drm: Remove duplicate drm_mode_cea_vic() Thierry Reding
2013-02-22 7:03 ` [PATCH v5 2/9] drm: Move mode tables to drm_edid.c Thierry Reding
2013-02-22 7:03 ` [PATCH v5 3/9] drm: Add some missing forward declarations Thierry Reding
2013-02-22 7:03 ` [PATCH v5 4/9] video: Add generic HDMI infoframe helpers Thierry Reding
2013-02-22 16:01 ` Ville Syrjälä [this message]
2013-03-04 14:49 ` Ville Syrjälä
2013-03-04 15:02 ` Thierry Reding
2013-03-07 13:32 ` Lucas Stach
2013-03-07 13:44 ` Thierry Reding
2013-04-08 11:52 ` Ville Syrjälä
2013-04-08 12:49 ` Thierry Reding
2013-02-22 7:03 ` [PATCH v5 5/9] drm: Add " Thierry Reding
2013-02-22 7:03 ` [PATCH v5 6/9] drm: Add EDID helper documentation Thierry Reding
2013-02-22 7:03 ` [PATCH v5 7/9] drm/tegra: Use generic HDMI infoframe helpers Thierry Reding
2013-02-22 7:03 ` [PATCH v5 8/9] drm/i915: " Thierry Reding
2013-02-22 7:03 ` [PATCH v5 9/9] drm/radeon: " Thierry Reding
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=20130222160122.GP4469@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=thierry.reding@avionic-design.de \
/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