On Sun, Feb 22, 2009 at 12:00:12PM +0000, Liam Girdwood wrote:
On Sun, 2009-02-22 at 00:36 +0100, Lennart Poettering wrote:
Now I'd of course prefer if the drivers get fixed to use a single element naming scheme only. Is there any chance to get that? And which one would that be?
This would likely be quite time consuming wrt to embedded drivers due to the complex audio hardware requirements of modern mobile phones. There are numerous hardware routes with different inputs and outputs and they are used in different combinations depending on use case.
I'd worry that it'd also have a negative impact on usability. People setting up scenarios and doing other device specific configuration often find it difficult to relate the controls visible in ALSA to the chip datasheet and keeping the names for the controls as close as possible to the datasheet helps deal with that quite a bit. If a standard naming were layered on top by something like the scenario manager this wouldn't be such an issue since device specific names would still be there and controls could be remapped dynamically depending on use case.
What would probably also help would be exposing information about the audio paths and how they relate to controls to user space but that doesn't look likely to happen any time soon.