From: Takashi Iwai Subject: Re: [RFC] Channel mapping API Date: Tue, 21 Aug 2012 19:09:32 +0200 Message-ID: References: <50337316.4080208@ladisch.de> <50339485.30500@canonical.com> <20120821140648.GC21557@sirena.org.uk> <503397A1.4000409@canonical.com> <20120821141759.GO7995@opensource.wolfsonmicro.com> <5033A0AD.2010403@canonical.com> <20120821150720.GS7995@opensource.wolfsonmicro.com> <5033AB74.8050201@canonical.com> <20120821163414.GV7995@opensource.wolfsonmicro.com> 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 192C7265B59 for ; Tue, 21 Aug 2012 19:09:31 +0200 (CEST) In-Reply-To: <20120821163414.GV7995@opensource.wolfsonmicro.com> 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: Mark Brown Cc: alsa-devel@alsa-project.org, Clemens Ladisch , David Henningsson List-Id: alsa-devel@alsa-project.org At Tue, 21 Aug 2012 17:34:15 +0100, Mark Brown wrote: > > On Tue, Aug 21, 2012 at 05:38:28PM +0200, David Henningsson wrote: > > On 08/21/2012 05:07 PM, Mark Brown wrote: > > > >Which of course is also replicated with the calls into the original > > >jack API. > > > Actually, the phantom jacks are only in the ctljack API. I > > deliberately left them out of the old jack API, because it was > > deprecated (or at least so I thought). > > Like I say it seems like the wrong way round to do things - we've got a > reasonable set of drivers using the jack API and a single driver using > the ctljack API, with the ctljack API being very much a subset of the > jack API (in that it only supports disconnected boolean values). I > still don't understand why it was ever implemented as a separate API. The API itself doesn't restrict the boolean -- it's a control element after all. The reason for ctljack API was stated many times: it came because of shortcomings of the jack API regarding the multiple items. For example, when multiple pins with the same type exist (e.g. typical for HD-audio), no standard way to resolve that. Or, if multiple cards provide the same name of jacks, we don't know which device is for which card. But, it's basically irrelevant with the channel map API discussion. Takashi