Skip to contentSkip to conversation

Passing audio info from HDMI EDID beside speaker allocation

DISCUSSION Patrick Lai 3 participants 6 messages Oct 5, 2012 – Oct 23, 2012

lore
Share & tools
lore
#0 lore 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

Signature · 2 lines
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
#1 lore raw
Quoted 9 lines · Patrick Lai

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?

Quoted 3 lines

Thanks
Patrick

Does anyone else have feedback for my query to Takashi?

Signature · 2 lines
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
#2 lore raw
In reply to Patrick Lai

At Thu, 04 Oct 2012 23:50:20 -0700,

Quoted 9 lines · Patrick Lai

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?

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.

Takashi

#3 lore raw
Quoted 3 lines · Takashi Iwai

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.

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?

Quoted 4 lines

Takashi

Signature · 2 lines
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
#4 lore raw

At Mon, 22 Oct 2012 11:00:02 -0700,

Quoted 11 lines · Patrick Lai
Quoted 3 lines · Takashi Iwai

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.

Quoted 4 lines

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

#5 lore raw
Quoted 12 lines
Quoted 9 lines
Quoted 4 lines

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.

Quoted 8 lines
Quoted 4 lines

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..