Wim Taymans 5de7898808 node: implement activation ... Make an eventfd for each node and listen for events when the node is activated. Reorganize some graphs links to make it possible to activiate nodes by signaling the eventfd Pass the peer node to each remote node and let the remote node directly activate the peer when needed. Let each node signal the driver node when finished. With this we don't need to go through the daemon to schedule the graph, nodes will simply activate eachother. We only go to the server when there is a server node to schedule. Keep stats about the state of each node and the time it was triggered, running and finished.		2019-02-12 17:42:33 +01:00
..
alsa-device.c	param: add some docs	2019-01-18 13:37:41 +01:00
alsa-monitor.c	pod: improve parser and builder	2019-01-22 17:38:23 +01:00
alsa-sink.c	reorganize some struct members to remove holes	2019-02-08 12:01:50 +01:00
alsa-source.c	node: implement activation	2019-02-12 17:42:33 +01:00
alsa-utils.c	node: implement activation	2019-02-12 17:42:33 +01:00
alsa-utils.h	Don't use __ in defines or declarations, it's reserved	2019-01-14 13:00:00 +01:00
alsa.c	use SPA_EXPORT to export symbols	2019-02-06 13:24:41 +01:00
meson.build	device: add device object	2018-11-23 12:43:47 +01:00