From: Takashi Iwai Subject: Re: Multiple channels mapping Date: Fri, 10 Feb 2012 12:05:53 +0100 Message-ID: References: <4F31C988.3090201@codeaurora.org> <4F323DE5.4050108@ladisch.de> <4F325D41.50304@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 C36B31038D4 for ; Fri, 10 Feb 2012 12:05:55 +0100 (CET) In-Reply-To: <4F325D41.50304@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 , Mark Brown List-Id: alsa-devel@alsa-project.org At Wed, 08 Feb 2012 12:32:17 +0100, Clemens Ladisch wrote: > > Takashi Iwai wrote: > > 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? > > There is one media controller device node per device (= ALSA card), > containing multiple entities (similar to how a ctl device contains > multiple controls). /dev/media42 _is_ separate, but the entity that > represents a PCM device is handled by the PCM code, so it would be > possible to have a shortcut to get a PCM device's TLVs directly. My concern is that accessing to different device files via yet another API in alsa-lib would be unnecessary overhead. (Since such information is demanded to be accessed through the normal ALSA API, we need a support in alsa-lib, anyway. > > More question is whether this information should be available before > > or after hw_params setup. > > This is pretty much static information, which is available even when the > PCM device isn't opened. If it's a static information that can be represented in TLV, we can provide it via the existing control API? Meanwhile, the channel-mapping isn't always static. As Mark suggested, the channel mapping can be changed dynamically later. Some HD-audio codec allows it, and HD-audio controller allows the arbitrary stereo-wise mapping, too. So, how flexible should it be -- it's a big question. If it's completely free-mappable, a style like TLV doesn't fit at all. In that case, we may need some mechanism like hw_constraint, too. OTOH, If it's something to select, providing a list of available modes would be feasible. > > BTW, the channel-mapping info can be useful for the automatic plug > > layer, too. > > And if there is a need for channel mapping information of ALSA plugins, > there needs to be a userspace library for the media controller API. I believe we need the alsa-lib, especially plugin access. thanks, Takashi