From mboxrd@z Thu Jan 1 00:00:00 1970 From: pl bossart Subject: Re: [PATCH] ALSA: HDA: Add jack detection for HDMI Date: Wed, 18 May 2011 10:43:36 -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 B70652437B for ; Wed, 18 May 2011 17:43:37 +0200 (CEST) Received: by ewy6 with SMTP id 6so532103ewy.38 for ; Wed, 18 May 2011 08:43:37 -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 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. I started doing some work on this, adding a persistent 256-byte buffer to store the ELD data instead of dynamically allocating and freeing the buffer. I am kind of lost with the controls though, never looked at this part of ALSA before. In all the HDA code, all controls have an IFACE_MIXER type, while all the code that uses ELEM_TYPE_BYTES the type is IFACE_PCM. Does this matter at all? Likewise, there's a 'generic_hdmi_build_controls' routine in which I could add the ELD control, but it uses cvt structures. I think it would make more sense to relate ELD controls to pins, as done with the proc information. Quite a learning experience...