lkml.org 
[lkml]   [2016]   [Dec]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH v5 11/14] ASoC: add simple-graph-card document
On Mon, Dec 5, 2016 at 6:57 PM, Kuninori Morimoto
<kuninori.morimoto.gx@renesas.com> wrote:
>
> 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 ?

Yes, something like this.

> in driver point of view, "I2S" is sound card here.

Well, that seems odd to me because I2S should just be the h/w block
that interfaces to I2S/SSI signals. I'd expect you still have a card
node that references these nodes. Maybe it just references the DSP and
then you walk the graph from there to find the I2S controller and
codec.

>
> 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>;
> }
> }
> }

\
 
 \ /
  Last update: 2016-12-06 16:04    [W:0.045 / U:1.304 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site