class Topology

Unique ID for this topology. The scope of this id is only within the `SignalProcessing`

protocol lifespan, i.e. until the channel associated with the protocol is closed.

Required.

Unique ID for this topology. The scope of this id is only within the `SignalProcessing`

protocol lifespan, i.e. until the channel associated with the protocol is closed.

Required.

Unique ID for this topology. The scope of this id is only within the `SignalProcessing`

protocol lifespan, i.e. until the channel associated with the protocol is closed.

Required.

Vector of processing elements edge pairs that specify connections between elements.

Processing elements are connected by edge pairs, to form multi-element pipelines.

A Topology can contain more than one distinct pipeline: the Topology need not be a single

interconnected sequence (e.g. Topology A->B->C D->E->F is valid).

To define multiple possible configurations where one possibility can be selected by the

client, return multiple `Topology` entries in `GetTopologies`.

If a device does support multiple Topology entries, then each specific Topology is not

required to include every Element. However, every element must be included in at least one

Topology.

Within each Topology, every sequence of connected elements must begin with an element

of type DAI_INTERCONNECT or RING_BUFFER, and must end with an element of type

DAI_INTERCONNECT or RING_BUFFER.

An DAI_INTERCONNECT element is _permitted_ to be the endpoint for an element sequence, but a

RING_BUFFER is _required_ to be one. If a certain RING_BUFFER element is listed in an

EdgeList entry as a `processing_element_id_from`, then within that Topology this same

element must NOT be listed in another EdgeList entry as a `processing_element_id_to` (and

vice versa).

As a special case, a DAI_INTERCONNECT element can refer to itself; i.e. an EdgePair may

contain `processing_element_id_from` and `processing_element_id_to` values that are equal.

However, this element must not _also_ connect to _other_ elements within the Topology (this

EdgePair must be the only one in `processing_elements_edge_pairs` to mention that element).

Required. Must contain at least one entry.

Vector of processing elements edge pairs that specify connections between elements.

Processing elements are connected by edge pairs, to form multi-element pipelines.

A Topology can contain more than one distinct pipeline: the Topology need not be a single

interconnected sequence (e.g. Topology A->B->C D->E->F is valid).

To define multiple possible configurations where one possibility can be selected by the

client, return multiple `Topology` entries in `GetTopologies`.

If a device does support multiple Topology entries, then each specific Topology is not

required to include every Element. However, every element must be included in at least one

Topology.

Within each Topology, every sequence of connected elements must begin with an element

of type DAI_INTERCONNECT or RING_BUFFER, and must end with an element of type

DAI_INTERCONNECT or RING_BUFFER.

An DAI_INTERCONNECT element is _permitted_ to be the endpoint for an element sequence, but a

RING_BUFFER is _required_ to be one. If a certain RING_BUFFER element is listed in an

EdgeList entry as a `processing_element_id_from`, then within that Topology this same

element must NOT be listed in another EdgeList entry as a `processing_element_id_to` (and

vice versa).

As a special case, a DAI_INTERCONNECT element can refer to itself; i.e. an EdgePair may

contain `processing_element_id_from` and `processing_element_id_to` values that are equal.

However, this element must not _also_ connect to _other_ elements within the Topology (this

EdgePair must be the only one in `processing_elements_edge_pairs` to mention that element).

Required. Must contain at least one entry.

Vector of processing elements edge pairs that specify connections between elements.

Processing elements are connected by edge pairs, to form multi-element pipelines.

A Topology can contain more than one distinct pipeline: the Topology need not be a single

interconnected sequence (e.g. Topology A->B->C D->E->F is valid).

To define multiple possible configurations where one possibility can be selected by the

client, return multiple `Topology` entries in `GetTopologies`.

If a device does support multiple Topology entries, then each specific Topology is not

required to include every Element. However, every element must be included in at least one

Topology.

Within each Topology, every sequence of connected elements must begin with an element

of type DAI_INTERCONNECT or RING_BUFFER, and must end with an element of type

DAI_INTERCONNECT or RING_BUFFER.

An DAI_INTERCONNECT element is _permitted_ to be the endpoint for an element sequence, but a

RING_BUFFER is _required_ to be one. If a certain RING_BUFFER element is listed in an

EdgeList entry as a `processing_element_id_from`, then within that Topology this same

element must NOT be listed in another EdgeList entry as a `processing_element_id_to` (and

vice versa).

As a special case, a DAI_INTERCONNECT element can refer to itself; i.e. an EdgePair may

contain `processing_element_id_from` and `processing_element_id_to` values that are equal.

However, this element must not _also_ connect to _other_ elements within the Topology (this

EdgePair must be the only one in `processing_elements_edge_pairs` to mention that element).

Required. Must contain at least one entry.