From: Patrick Lai <plai@codeaurora.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Passing audio info from HDMI EDID beside speaker allocation
Date: Thu, 04 Oct 2012 23:50:20 -0700 [thread overview]
Message-ID: <506E832C.50702@codeaurora.org> (raw)
Hi Takashi,
You proposed snd_pcm_query_chmaps() to query underlying hardware
speaker allocation. Please correct me if I have wrong understanding of
this API. On the other hand, HDMI EDID contains audio data other than
speaker allocation such as audio formats(LPCM, AC3, and etc). How are
these information other than speaker allocation passed back to the
user-space? Are there a standard kernel and alsa query interfaces now?
Thanks
Patrick
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next reply other threads:[~2012-10-05 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 6:50 Patrick Lai [this message]
2012-10-08 6:18 ` Passing audio info from HDMI EDID beside speaker allocation 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
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=506E832C.50702@codeaurora.org \
--to=plai@codeaurora.org \
--cc=alsa-devel@alsa-project.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 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).