On Fri, Jun 07, 2024 at 04:15:01AM +0000, Kuninori Morimoto wrote: > Some Sound Card might need special trigger ordering which is based on > CPU/Codec connection. It is already supported on ASoC, but Simple Audio > Card / Audio Graph Card still not support it. Let's support it. I have no idea what trigger order means reading this patch. > > Cc: Maxim Kochetkov <fido_max@xxxxxxxx> > Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@xxxxxxxxxxx> > --- > .../devicetree/bindings/sound/audio-graph-port.yaml | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/Documentation/devicetree/bindings/sound/audio-graph-port.yaml b/Documentation/devicetree/bindings/sound/audio-graph-port.yaml > index 28b27e7e45de6..d1cbfc5edd3ac 100644 > --- a/Documentation/devicetree/bindings/sound/audio-graph-port.yaml > +++ b/Documentation/devicetree/bindings/sound/audio-graph-port.yaml > @@ -25,6 +25,15 @@ definitions: > capture-only: > description: port connection used only for capture > $ref: /schemas/types.yaml#/definitions/flag > + link-trigger-order: > + description: trigger order for both start/stop > + $ref: /schemas/types.yaml#/definitions/uint32-array > + link-trigger-order-start: > + description: trigger order for start > + $ref: /schemas/types.yaml#/definitions/uint32-array > + link-trigger-order-stop: > + description: trigger order for stop > + $ref: /schemas/types.yaml#/definitions/uint32-array constraints? These are just definitions. Where are the properties defined? > > endpoint-base: > allOf: > -- > 2.43.0 >
