From: Takashi Iwai Subject: Re: Multiple channels mapping Date: Wed, 08 Feb 2012 10:23:45 +0100 Message-ID: References: <4F31C988.3090201@codeaurora.org> <4F323DE5.4050108@ladisch.de> 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 9C0EC103D92 for ; Wed, 8 Feb 2012 10:23:47 +0100 (CET) In-Reply-To: <4F323DE5.4050108@ladisch.de> 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: Clemens Ladisch Cc: alsa-devel List-Id: alsa-devel@alsa-project.org At Wed, 08 Feb 2012 10:18:29 +0100, Clemens Ladisch wrote: > > Takashi Iwai wrote: > > 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. > > TLVs on media controller entities. Well, my concern is that it might be too far from the other PCM stuff. How the implementation would look like? BTW, the channel-mapping info can be useful for the automatic plug layer, too. It would re-route the channels when not following ALSA-standard maps automatically, for example. (Remember some old AC97 chips.) More question is whether this information should be available before or after hw_params setup. thanks, Takashi