Hi,
On Friday 10 May 2013 21:53:30 Mark Brown wrote:
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 like to help out, but I'm also unfamiliar with UCM profiles. This configuation belong to the AC100 netboot (board name paz00) and a single hifi use case would be sufficient for now. http://www.alsa- project.org/main/index.php/Use_Case_Manager doesn't give much info. Andrey, Leon, any idea?
Marc
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.