From: Sameer Pujar <spujar@nvidia.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Rob Herring <robh+dt@kernel.org>, Mark Brown <broonie@kernel.org>,
<alsa-devel@alsa-project.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] ASoC: dt-bindings: audio-graph-card: switch to yaml base Documentation
Date: Mon, 26 Oct 2020 08:19:59 +0530 [thread overview]
Message-ID: <963ea81c-f1c4-580c-f336-f9e5a98d2cae@nvidia.com> (raw)
In-Reply-To: <873621lxhv.wl-kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
>>> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>>>
>>> This patch switches from .txt base to .yaml base Document.
>>>
>>> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>>> ---
>>> .../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.
next prev parent reply other threads:[~2020-10-26 2:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 0:45 [PATCH v3 0/3] ASoC: dt-bindings: audio-graph-card: switch to yaml base Documentation Kuninori Morimoto
2020-10-22 0:46 ` [PATCH v3 1/3] " Kuninori Morimoto
2020-10-22 5:19 ` Sameer Pujar
2020-10-27 4:52 ` Kuninori Morimoto
2020-10-27 6:15 ` Sameer Pujar
2020-10-27 5:32 ` Kuninori Morimoto
2020-10-27 6:03 ` Sameer Pujar
2020-10-28 16:04 ` Rob Herring
2020-10-28 23:33 ` Kuninori Morimoto
2020-10-23 13:52 ` Sameer Pujar
2020-10-25 23:07 ` Kuninori Morimoto
2020-10-26 2:49 ` Sameer Pujar [this message]
2020-10-27 5:22 ` Kuninori Morimoto
2020-10-22 0:46 ` [PATCH v3 2/3] ASoC: dt-bindings: renesas,rsnd: " Kuninori Morimoto
2020-10-23 16:06 ` [PATCH v3 2/3] ASoC: dt-bindings: renesas, rsnd: " Rob Herring
2020-10-22 0:46 ` [PATCH v3 3/3] dt-bindings: ASoC: renesas,rsnd: Add r8a77961 support Kuninori Morimoto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=963ea81c-f1c4-580c-f336-f9e5a98d2cae@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).