From: Rob Herring <robh@kernel.org>
To: Alexander Stein <alexander.stein@mailbox.org>
Cc: devicetree@vger.kernel.org, Mark Brown <broonie@kernel.org>,
alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH v2 3/3] ASoC: meson: g12a: add missing sound-name-prefix property
Date: Tue, 21 Dec 2021 15:53:47 -0400 [thread overview]
Message-ID: <YcIwy0B7Xm3MDF1s@robh.at.kernel.org> (raw)
In-Reply-To: <20211218143423.18768-3-alexander.stein@mailbox.org>
On Sat, 18 Dec 2021 15:34:23 +0100, Alexander Stein wrote:
> This is used in meson-sm1 and meson-g12 .dtsi. Add the property to
> the binding.
> This fixes the dtschema warning:
> audio-controller@740: 'sound-name-prefix' does not match any of the
> regexes: 'pinctrl-[0-9]+'
>
> Signed-off-by: Alexander Stein <alexander.stein@mailbox.org>
> ---
> All users have set this to "TOACODEC", but I am not sure if this value is
> mandatory, so I opted to not set a pattern for this property.
>
> Changes in v2:
> * Fix 'pass' -> 'true'
>
> .../devicetree/bindings/sound/amlogic,g12a-toacodec.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-12-21 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 14:34 [PATCH v2 1/3] ASoC: dt-bindings: Use name-prefix schema Alexander Stein
2021-12-18 14:34 ` [PATCH v2 2/3] ASoC: meson: t9015: add missing sound-name-prefix property Alexander Stein
2021-12-21 19:53 ` Rob Herring
2021-12-18 14:34 ` [PATCH v2 3/3] ASoC: meson: g12a: " Alexander Stein
2021-12-21 19:53 ` Rob Herring [this message]
2021-12-21 12:36 ` [PATCH v2 1/3] ASoC: dt-bindings: Use name-prefix schema Jerome Brunet
2021-12-21 19:53 ` Rob Herring
2021-12-22 14:04 ` 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=YcIwy0B7Xm3MDF1s@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alexander.stein@mailbox.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.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;
as well as URLs for NNTP newsgroup(s).