On Mon, Nov 28, 2016 at 02:48:37AM +0000, Kuninori Morimoto wrote:
From: Kuninori Morimoto kuninori.morimoto.gx@renesas.com
Signed-off-by: Kuninori Morimoto kuninori.morimoto.gx@renesas.com
.../bindings/sound/simple-graph-scu-card.txt | 69 ++++++++++++++++++++++ 1 file changed, 69 insertions(+) create mode 100644 Documentation/devicetree/bindings/sound/simple-graph-scu-card.txt
diff --git a/Documentation/devicetree/bindings/sound/simple-graph-scu-card.txt b/Documentation/devicetree/bindings/sound/simple-graph-scu-card.txt new file mode 100644 index 0000000..b0e46ba --- /dev/null +++ b/Documentation/devicetree/bindings/sound/simple-graph-scu-card.txt @@ -0,0 +1,69 @@ +Simple-Graph-SCU-Card:
+Simple-Graph-SCU-Card specifies audio DAI connections of SoC <-> codec. +It is based on common bindings for device graphs. +see ${LINUX}/Documentation/devicetree/bindings/graph.txt
+Basically, Simple-Graph-SCU-Card property is same as Simple-Card / Simple-Graph-Card. +see ${LINUX}/Documentation/devicetree/bindings/sound/simple-card.txt
- ${LINUX}/Documentation/devicetree/bindings/sound/simple-graph-card.txt
+Main difference between Simple-Graph-Card and Simple-Graph-SCU-Card is that +Simple-Graph-SCU-Card can use multi CPU.
So it can have more that 1 port? At least for the bindings, I think you should combine these 2 bindings. Whether the driver should be combined is separate question. I imagine you have 2 compatible strings because you have 2 drivers, but that isn't really a reason to have 2.
I still have no idea what SCU is.
Rob