On 08/24/2016 01:41 AM, Mark Brown wrote:
On Fri, Aug 19, 2016 at 06:12:55PM +0800, mengdong.lin@xxxxxxxxxxxxxxx wrote:
Definition of dynamic PCM trigger ordering is exposed to uapi asoc.h,
and topology allows user space to define the trigger ordering for PCM
(FE links).
This seems *incredibly* implementation specific. Why wouldn't the
driver for the thing implementing the topology be able to figure out the
ordering here? What's the use case? What happens when we change away
from DPCM?
I'll check if we can let driver figure out this ordering or use some
more generic name.
We add this trigger ordering as driver developer request and we think
it's decided by the firmware behavior. We hope firmware properties can
be covered by topology.
Thanks
Mengdong
_______________________________________________
Alsa-devel mailing list
Alsa-devel@xxxxxxxxxxxxxxxx
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
