Hi Rob
> We have 2 different meanings for channel-map-index here. We have the
> codecs defining "I am index N" and then the CPUs defining "I'm connected
> to codec N". That's confusing to start with. Made-up indices are
> something we try to avoid in DT. Are the numbers here (0, 1, 2)
> significant? The normal way we link from one node to another is
> phandles. Why not use phandles here:
>
> CPUA { ... .channel-map-index = <&CodecA>; }
> CPUB { ... .channel-map-index = <&CodecB &CodecC>; }
>
>
> However, we also have OF graph to define complex topologies/connections
> AND we're already using it for this binding. So why not here? You can
> always have more than 1 port and/or endpoint. Generally, multiple ports
> are independent/simultaneous data connections and multiple endpoints are
> either 1:N fanout or N:1 muxed connections.
Hmm... I will re-consider about it.
Thank you for your help !!
Best regards
---
Kuninori Morimoto
