[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h96hc1us.wl%kuninori.morimoto.gx@renesas.com>
Date: Tue, 6 Dec 2016 00:57:19 +0000
From: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
To: Rob Herring <robh@...nel.org>
CC: Mark Brown <broonie@...nel.org>,
Linux-ALSA <alsa-devel@...a-project.org>,
Liam Girdwood <lgirdwood@...il.com>,
Simon <horms@...ge.net.au>,
Laurent <laurent.pinchart@...asonboard.com>,
Guennadi <g.liakhovetski@....de>,
"Grant Likely" <grant.likely@...aro.org>,
Frank Rowand <frowand.list@...il.com>,
Linux-DT <devicetree@...r.kernel.org>,
Linux-Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 11/14] ASoC: add simple-graph-card document
Hi Rob
> I'd expect the top level node to be the card node that knows how to find
> all the components. The graph should reflect the data flow. For example,
> the data goes to audio DSP to I2S host to codec to amp.
Do you mean, is this OK for OF graph ?
in driver point of view, "I2S" is sound card here.
I2S {
port {
i2s-dsp: endpoint {
remote-endpoint = <&dsp>;
}
i2s-codec: endpoint {
remote-endpoint = <&codec>;
}
}
}
DSP {
port {
dsp: endpoint {
remote-endpoint = <&i2s-dsp>;
}
}
}
Codec {
port {
codec: endpoint {
remote-endpoint = <&i2s-codec>;
}
}
}
Powered by blists - more mailing lists