From: Takashi Iwai Subject: Re: Passing audio info from HDMI EDID beside speaker allocation Date: Tue, 23 Oct 2012 14:16:57 +0200 Message-ID: References: <506E832C.50702@codeaurora.org> <508589A2.4080309@codeaurora.org> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 563122652B9 for ; Tue, 23 Oct 2012 14:16:58 +0200 (CEST) In-Reply-To: <508589A2.4080309@codeaurora.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Patrick Lai Cc: alsa-devel List-Id: alsa-devel@alsa-project.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