On Fri, May 10, 2013 at 10:22:59AM -0600, Stephen Warren wrote:
> "alc5632" is the name of the audio CODEC, which could be used in a
> variety of different boards, each of which might require a different UCM
> configuration. Shouldn't the file be named based on the board name. At
Yes, it should.
> I also notice that this file doesn't define any use-cases/verbs/...
> Presumably a Linux-based OS would expect a certain set of them to exist,
> and they'd be implemented/named consistently across all UCM configs?
I'd expect them to at least fall back to assuming some default thing is
available - having a model that is more "do I need to do something
special for this mode". Being able to give at least some basic
functionality from a minimal starting point seems sensible.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20130510/dbd1c4e2/attachment.sig>