From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: arun.raghavan@collabora.co.uk, Patrick Lai <plai@codeaurora.org>,
alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Passing audio info from HDMI EDID beside speaker allocation
Date: Tue, 23 Oct 2012 17:56:33 -0500 [thread overview]
Message-ID: <508720A1.80208@linux.intel.com> (raw)
In-Reply-To: <s5hmwzdids6.wl%tiwai@suse.de>
>>> In the case of HD-audio, it's passed via the normal IEC958 status bits
>>> controls separately. ELD itself is exposed as a byte array in a
>>> control element, but it's read-only.
>>
>> Thanks for the reply. Couple more questions
>>
>> 1. Is kcontrol "ELD" being read directly by application or there is
>> ALSA library API to parse the information.
>
> Nothing so far. It's just a raw data.
>
>> 2. Also, I see you submit this patch [PATCH 3/3] ELD proc interface for
>> HDMI sinks in 2008. I presume it's just for information purpose. You
>> still expect application to query for HDMI sink capability through
>> "ELD" kcontrol. Am I correct?
>
> It's not prohibited for apps to parse the proc interface but it's not
> guaranteed to be stable :) So yes, parsing ELD manually would be a
> safer way.
I wrote some code to parse the ELD kcontrol to enable passthrough if AC3
is supported by the receiver, I believe it's been integrated by Arun in
a branch of PulseAudio. It's probably 1 year old now..
prev parent reply other threads:[~2012-10-23 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 6:50 Passing audio info from HDMI EDID beside speaker allocation Patrick Lai
2012-10-08 6:18 ` Patrick Lai
2012-10-08 8:20 ` Takashi Iwai
2012-10-22 18:00 ` Patrick Lai
2012-10-23 12:16 ` Takashi Iwai
2012-10-23 22:56 ` Pierre-Louis Bossart [this message]
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=508720A1.80208@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=arun.raghavan@collabora.co.uk \
--cc=plai@codeaurora.org \
--cc=tiwai@suse.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 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.