Rework mixer calls to handle dependencies

Rework 'attach' mixer calls to handle dependencies individually.
That means that an attach call will be performed for each dependency.

To avoid errors when calling mixer, complete list of dependencies
should be send to it, but we can specify which dependency
we want to be processed using 'handled' key.

BUG-AGL: SPEC-2887

Change-Id: I9db7391fe7a44ba045fd82d94221a1442b7c2198
Signed-off-by: Jonathan Aillet <jonathan.aillet@iot.bzh>

1 files changed, 9 insertions, 0 deletions

diff --git a/lib/4a-hal-utilities/4a-hal-utilities-data.h b/lib/4a-hal-utilities/4a-hal-utilities-data.h
index e57bd85..38cade6 100644
--- a/lib/4a-hal-utilities/4a-hal-utilities-data.h
+++ b/lib/4a-hal-utilities/4a-hal-utilities-data.h
@@ -56,6 +56,14 @@ enum ProbedDeviceClasses {
 	MANDATORY_PROBED_DEVICE = 3
 };
 
+// Enum for dependencies mixer link status
+enum DependencyMixerStatus {
+	DEPENDENCY_NO_MIXER_LINK = 0,
+	DEPENDENCY_MIXER_LINK_USELESS = 1,
+	DEPENDENCY_MIXER_ATTACH_SUCCEED = 2,
+	DEPENDENCY_MIXER_ATTACH_FAILED = 3
+};
+
 // Enum for probed devices (dependencies) info format requested
 enum DependencyInfoJsonFormat {
 	DEPENDENCY_COMPACT_JSON = 0,
@@ -91,6 +99,7 @@ struct InternalHalProbedDevice {
 	json_object *requestedDeviceJ;
 
 	struct InternalHalDeviceData *deviceData;
+	enum DependencyMixerStatus mixerLinkStatus;
 
 	struct cds_list_head node;
 };