On 08/27/2014 05:14 AM, Kuninori Morimoto wrote:
Hi Mark again
But, How about this case ?
FE cpu: CPU-A
codec: Codec-A
BE cpu: CPU-B
codec: Codec-B
I found 1 method.
I can create it if we can assume that
"simple-card doen't support above style",
If the documentation refers to the interface as for example "I2S0" then
the DT should refer to it as I2S0 too.
simple-card is using "format" property now,
and I remember that someone want to exchange format in DPCM.
My 1st DPCM patch used "remote" property for specify FE/BE.
And, we can get DAI stream_name if we can update snd_soc_of_get_dai_name()
This means, we can use DPCM like below
if you can accept my previous "ASoC: dapm: enable DAI name on DAPM route"
What do you think ?
sound {
compatible = "simple-audio-card";
/* FrontEnd */
simple-audio-card,dai-link@0 {
...
format = "left_j";
remote = <&endpoint>;
cpu {
sound-dai = <&rcar_sound 0>;
};
codec { /* dummy */ };
};
/* BackEnd */
endpoint: simple-audio-card,dai-link@1 {
...
format = "left_j";
cpu { /* dummy */ };
codec1: codec {
sound-dai = <&ak4643>;
};
};
};
When you try to come up with with a binding try to completely ignore that
something call DPCM exists. The binding is supposed to describe the hardware
and how the different hardware components are interconnected. So try to come
up with a binding that accurately describes the hardware connections. Once
that is done try to map the binding onto the existing software framework.
The last step may require some adjustments to the framework.
- Lars
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
