From: Takashi Iwai Subject: Re: [RFC] Channel mapping API Date: Tue, 21 Aug 2012 21:23:45 +0200 Message-ID: References: <5033CD8D.6070002@linux.intel.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 726B4265D65 for ; Tue, 21 Aug 2012 21:23:45 +0200 (CEST) In-Reply-To: <5033CD8D.6070002@linux.intel.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: Pierre-Louis Bossart Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Tue, 21 Aug 2012 13:03:57 -0500, Pierre-Louis Bossart wrote: > > On 8/21/2012 5:31 AM, Takashi Iwai wrote: > > The additional alsa-lib API functions look like: > > > > int **snd_pcm_query_chmaps(snd_pcm_t *pcm); > > int *snd_pcm_get_chmap(snd_pcm_t *pcm); > > int snd_pcm_set_chmap(snd_pcm_t *pcm, const int *map); > Hi Takashi, > Maybe my question is slightly off-topic but can this be used by > applications relying on tinyALSA or tinyCompress? Looks like we will > need to replicate the same ideas based on TLV? Yes, the TLV parser code and conversion from the control element values to int array would be required. Other than that, the kernel ABI itself is just a re-use of the exiting infrastructure. Takashi