Re: [RFC] Channel mapping API

[David Henningsson <david.henningsson@canonical.com>]

On 08/21/2012 04:06 PM, Mark Brown wrote:
> On Tue, Aug 21, 2012 at 04:00:37PM +0200, David Henningsson wrote:
>> On 08/21/2012 01:37 PM, Clemens Ladisch wrote:
>
>>> This doesn't handle devices with simply numbered outputs (such as many
>>> ICE1712-based devices), or cases where one PCM channel can be routed to
>>> multiple outputs.  However, those devices typically have their own mixer
>>> applets, and generic applications aren't interested in configuring them.
>
>> As for routing more than one channel in the map from the same PCM,
>> that seems a bit more complex. Maybe one could do a bitmap of
>> channels instead of just one channel (with say, 32 room channel
>> positions and 32 just numbered positions, that would be 64 bits).
>> But how common is that anyway?
>
> It's very common on the embedded side to use pure numbered stuff (or at
> least to assign semantics dynamically at runtime which I suspect boils
> down to the same thing here).

It reminds me of the discussion we had about jack labelling (for HDA or 
everyone? I do not remember), where we ended up having

1) physical location (left side, internal, docking station)
2) type (headphone, speaker)
3) channel map (front, rear, c/lfe)

Maybe that's where this discussion is heading as well? I like the idea 
of having the same TLV description for jacks, mixer controls and PCM 
channels, maybe that could work for all but the most exotic cases?

(Where exotic means unusual hw on both the pro-audio and the embedded side)


-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic