From: Takashi Iwai <tiwai@suse.de>
To: Patrick Lai <plai@codeaurora.org>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Passing audio info from HDMI EDID beside speaker allocation
Date: Tue, 23 Oct 2012 14:16:57 +0200 [thread overview]
Message-ID: <s5hmwzdids6.wl%tiwai@suse.de> (raw)
In-Reply-To: <508589A2.4080309@codeaurora.org>
At Mon, 22 Oct 2012 11:00:02 -0700,
Patrick Lai wrote:
>
> On 10/8/2012 1:20 AM, Takashi Iwai wrote:
>
> > 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.
Takashi
next prev parent reply other threads:[~2012-10-23 12:16 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 [this message]
2012-10-23 22:56 ` Pierre-Louis Bossart
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=s5hmwzdids6.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=plai@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).