[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87wpfc38i2.wl-kuninori.morimoto.gx@renesas.com>
Date: Wed, 7 Dec 2016 00:10:49 +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
> > Do you mean, is this OK for OF graph ?
>
> Yes, something like this.
Wow!! Thanks !!
it makes new OF-graph easier !!
> > 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.
If my understanding was correct, this is good ?
Card {
ports {
port@0 {
card-dsp: endpoint {
remote-endpoint = <&dsp>;
};
};
port@1 {
card-codec: endpoint {
remote-endpoint = <&codec>;
};
}
}
}
DSP {
port {
dsp: endpoint {
remote-endpoint = <&card-dsp>;
}
}
}
Codec {
port {
codec: endpoint {
remote-endpoint = <&card-codec>;
}
}
}
Powered by blists - more mailing lists