On Thu, Feb 22, 2018 at 10:03:42AM +0000, Srinivas Kandagatla wrote:

On 22/02/18 00:14, Rob Herring wrote:

quoted

Am I saying a single DT node for this? Yes, perhaps.

Yes, I will give that a go.

So we will endup having something like this in DT for one frontend and
backend dailink:

Let's not start encoding DPCM into DT, DPCM is very much an
implemntation detail of the current stack which we're gradually pushing
towards replacing with something better.  What we want to be doing is
just treating components inside the SoC the same as components in a
CODEC, the routing within a SoC being the same as in a CODEC and
similarly for externally connected devices.

		fe at 1 {
                	is-fe;
                        link-name = "MultiMedia1";

In particular having the concept of "front end" in the DT is *very*
implementation specific.  We should just be describing the connections
that exist in the system.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180301/b8f7604e/attachment.sig>