From: Marek Vasut <marex@denx.de>
To: Mark Brown <broonie@kernel.org>
Cc: devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: dt-bindings: audio-graph-card: Expand 'widgets' documentation
Date: Thu, 15 Jun 2023 14:58:56 +0200 [thread overview]
Message-ID: <664102f3-e963-531a-5e39-b556ca132ece@denx.de> (raw)
In-Reply-To: <d40f2c63-0b8a-425e-90a9-dd8f552ba782@sirena.org.uk>
On 6/6/23 20:25, Mark Brown wrote:
> On Tue, Jun 06, 2023 at 07:59:51PM +0200, Marek Vasut wrote:
>
>> Document the encoding of 'widgets' property to avoid confusion.
>
>> widgets:
>> - description: User specified audio sound widgets.
>> + description: |
>> + User specified audio sound widgets.
>> + Each entry is a pair of strings, the first being the type of
>> + widget ("Microphone", "Line", "Headphone", "Speaker"), the
>> + second being the machine specific name for the widget.
>
> This looks sensible to me, I don't know if there's a way we can get the
> tooling to validate either the length or (ideally) the widget type
> strings?
It seems there is no way to do validation of every two elements for
lists with variable number of elements.
next prev parent reply other threads:[~2023-06-15 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 17:59 [PATCH] ASoC: dt-bindings: audio-graph-card: Expand 'widgets' documentation Marek Vasut
2023-06-06 18:25 ` Mark Brown
2023-06-15 12:58 ` Marek Vasut [this message]
2023-06-09 12:03 ` Mark Brown
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=664102f3-e963-531a-5e39-b556ca132ece@denx.de \
--to=marex@denx.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.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