From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: RFC: Jack-detection control elements on HD-audio Date: Fri, 19 Jun 2009 11:02:27 +0200 Message-ID: References: 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 mx1.suse.de (cantor.suse.de [195.135.220.2]) by alsa0.perex.cz (Postfix) with ESMTP id BEFB9103893 for ; Fri, 19 Jun 2009 11:02:27 +0200 (CEST) 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: Jaroslav Kysela Cc: alsa-devel@alsa-project.org, Lennart Poettering List-Id: alsa-devel@alsa-project.org At Fri, 19 Jun 2009 10:54:00 +0200 (CEST), Jaroslav Kysela wrote: > > On Fri, 19 Jun 2009, Takashi Iwai wrote: > > > Hi, > > > > yet another thing I've worked recently on is a bit more generalized > > framework for jack-sense reporting for HD-audio. This supersedes the > > existing jack-sense reporting via the input layer. In addition, it > > gives the corresponding control elements. > > > > For example, you'll have "Jack HP-Out" (or a bit more verbose like > > "Jack HP-Out at Ext Rear") control via control API as well as other > > mixer controls. This can notify when a jack is plugged/unplugged. > > But, another big win is that you can read the current pin sense just > > by reading this element. > > Before definining such extension, I would really see to define standard > control names in Documentation/ControlNames.txt file. It seems to me that > most new drivers does not follow suggested naming. The document should be > reviewed, of course. That's true. We definitely need a standard naming. But note that these controls are no mixers but provided as IFACE_CARD, so they won't pollute the mixer abstraction. So, it's rather the question of the user of these controls. Takashi