From mboxrd@z Thu Jan 1 00:00:00 1970 From: pl bossart Subject: Re: [PATCH] ALSA: HDA: Add jack detection for HDMI Date: Tue, 17 May 2011 15:51:13 -0500 Message-ID: References: <4DD27C43.3050509@canonical.com> <74CDBE0F657A3D45AFBB94109FB122FF04986AAA0D@HQMAIL01.nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mail-ew0-f51.google.com (mail-ew0-f51.google.com [209.85.215.51]) by alsa0.perex.cz (Postfix) with ESMTP id F204E1037EC for ; Tue, 17 May 2011 22:51:13 +0200 (CEST) Received: by ewy6 with SMTP id 6so283201ewy.38 for ; Tue, 17 May 2011 13:51:13 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Takashi Iwai Cc: ALSA Development Mailing List , Stephen Warren , David Henningsson List-Id: alsa-devel@alsa-project.org >> >> a) Is it possible to report more information alongside the plug event= s, >> >> such as ELD/EDID content? Or, is the idea that the kernel sends a plug >> >> event, and then user-space retrieves that information via some other >> >> API? I don't think there's an API to retrieve ELD information at pres= ent >> >> though right? Although certainly it'd make sense for that to be a >> >> completely separate patch. >> > >> > A simple approach would be adding a control element containing >> > byte-array of ELD/EDID. >> >> Are there any examples of such controls? Or are we talking about a new >> kind of control? > > Look for SNDRV_CTL_ELEM_TYPE_BYTES. =A0Some codecs provide these. Thanks for the pointer. looks simple enough to expose the ELD bytes. This type of element can store up to 512 bytes, enough to store the ELD header+baseline fields (260 bytes tops). I don't think userspace would want to muck with vendor-specific information? we may need an array of ELD controls in case there are several monitors. Not sure how to represent which one is actually used. The ELD is linked to a specific nid (node id), we'd need to link this to the audio device #?