On 11-01-2024 11:02, Kuninori Morimoto wrote:
port {
cpu_endpoint0: endpoint@0 { remote-endpoint = <&codec1_endpoint>; };
cpu_endpoint1: endpoint@1 { remote-endpoint = <&codec2_endpoint>; };
(snip)
Is it possible to have similar behavior with audio-graph-card?
Unfortunately, N:M connection is supported only Card2.
For 1:N connection, how many DAI links audio-graph-card2 driver creates?
(snip)
No, that is not what I am looking for. Let me please try to rephrase this.
Does audio-graph-card2 driver creates N+1 DAI links or a single DAI link?
Oh, I see. It can handle many DAI links. see [1].
One note here is some link is comment-outed here,
because it handles too many DAI links, it reached to the upper size limit.
What I am asking is, with audio-graph-card2, when you declare 1:N
connection in DT bindings, how many DAI links you create in the driver.
Is it like the audio-graph-card2 driver parses the whole 1:N connection
and creates only one DAI link in ASoC core or it breaks them into
multiple links and create N+1 DAI links in ASoC core?
In other words,
1:N connection in DT == 1 DAI link in ASoC core?
Or
1:N connection in DT == N+1 DAI links in ASoC core?
