Hi Morimoto-san,
From: Kuninori Morimoto <kuninori.morimoto.gx@xxxxxxxxxxx>
This patch switches from .txt base to .yaml base Document.
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@xxxxxxxxxxx>
---
.../bindings/sound/audio-graph-card.txt | 337 ------------------
.../bindings/sound/audio-graph-card.yaml | 165 +++++++++
.../devicetree/bindings/vendor-prefixes.yaml | 2 +-
3 files changed, 166 insertions(+), 338 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/sound/audio-graph-card.txt
create mode 100644 Documentation/devicetree/bindings/sound/audio-graph-card.yaml
...
+
+ port:
+ description: single OF-Graph subnode
+ type: object
+ properties:
+ reg:
+ maxItems: 1
+ prefix:
+ description: "device name prefix"
+ $ref: /schemas/types.yaml#/definitions/string
+ convert-rate:
+ description: CPU to Codec rate convert.
+ $ref: /schemas/types.yaml#/definitions/uint32
+ convert-channels:
+ description: CPU to Codec rate channels.
+ $ref: /schemas/types.yaml#/definitions/uint32
+ patternProperties:
+ "^endpoint(@[0-9a-f]+)?":
+ $ref: "#/properties/endpoint"
+
+ ports:
+ description: multi OF-Graph subnode
+ type: object
+ patternProperties:
+ "^port(@[0-9a-f]+)?":
+ $ref: "#/properties/port"
+
Can these be referenced from graph.yaml (port and ports properties)
and only additonal properties (specific to audio-graph) could be
populated here?
Yes of course.
In such case, I need to wait graph.yaml first I think.
Yes we first need to add graph.yaml, which I started to add in series
https://lkml.org/lkml/2020/10/16/645
Since there is cyclic dependency between your patch and my series, I
could probably pull out graph.yaml out of my series and independently
submit that first.
