From: Takashi Iwai Subject: Re: Multiple channels mapping Date: Wed, 08 Feb 2012 09:58:52 +0100 Message-ID: References: <4F31C988.3090201@codeaurora.org> 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 A225C24598 for ; Wed, 8 Feb 2012 09:58:52 +0100 (CET) In-Reply-To: <4F31C988.3090201@codeaurora.org> 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: Patrick Lai Cc: alsa-devel List-Id: alsa-devel@alsa-project.org At Tue, 07 Feb 2012 17:02:00 -0800, Patrick Lai wrote: > > Hi, > > The DSP I am working on supports channel assignments similar to ALSA > route plug-in described in this link http://drona.csa.iisc.ernet.in > /~uday/alsamch.shtml. > I am currently looking a way to pass channel/speaker mapping > information of PCM stream( i.c channel 0 -> Front Left speaker, channel > 1 -> Front Right speaker) to ALSA driver. I looked at latest kernel > tree and don't think there is already provision for my purpose. Can > anyone confirm? If I were to improvise a way to pass channel/speaker > mapping information, should I follow the same approach similar to how > bits per sample and other hardware parameter is passed? Currently the channel-mapping information is a missing piece in ALSA framework, and it's a very long-standing item on my TODO list. The implementation itself should be easy, but the only question is the API design. If you have a good proposal, please speak up. thanks, Takashi