From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Paweł Anikiel" <pan@semihalf.com>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, lgirdwood@gmail.com,
broonie@kernel.org
Cc: perex@perex.cz, tiwai@suse.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, dinguyen@kernel.org,
lars@metafoo.de, nuno.sa@analog.com, upstream@semihalf.com,
amstan@chromium.org
Subject: Re: [PATCH v2 4/7] ASoC: dt-bindings: Add Google Chameleon v3 audio codec
Date: Tue, 9 May 2023 08:18:15 +0200 [thread overview]
Message-ID: <b8306c55-8551-4c86-f85d-3aebe1ad0ca1@linaro.org> (raw)
In-Reply-To: <20230508113037.137627-5-pan@semihalf.com>
On 08/05/2023 13:30, Paweł Anikiel wrote:
> Add binding for google,chv3-codec device.
>
> Signed-off-by: Paweł Anikiel <pan@semihalf.com>
> ---
> .../bindings/sound/google,chv3-codec.yaml | 31 +++++++++++++++++++
> 1 file changed, 31 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sound/google,chv3-codec.yaml
>
> diff --git a/Documentation/devicetree/bindings/sound/google,chv3-codec.yaml b/Documentation/devicetree/bindings/sound/google,chv3-codec.yaml
> new file mode 100644
> index 000000000000..5329dc140b1c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/google,chv3-codec.yaml
> @@ -0,0 +1,31 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/sound/google,chv3-codec.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Google Chameleon v3 audio codec
> +
> +maintainers:
> + - Paweł Anikiel <pan@semihalf.com>
> +
> +allOf:
> + - $ref: dai-common.yaml#
> +
> +properties:
> + compatible:
> + const: google,chv3-codec
> +
> + "#sound-dai-cells":
> + const: 0
No supplies? How do you get power?
> +
> +required:
> + - compatible
> +
> +additionalProperties: false
unevaluatedProperties: false, because you might want to use name-prefix.
> +
> +examples:
> + - |
> + audio-codec {
> + compatible = "google,chv3-codec";
Extend the example with dai-cells.
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-05-09 6:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 11:30 [PATCH v2 0/7] Add Chameleon v3 ASoC audio Paweł Anikiel
2023-05-08 11:30 ` [PATCH v2 1/7] ASoC: Add Google Chameleon v3 i2s driver Paweł Anikiel
2023-05-08 11:30 ` [PATCH v2 2/7] ASoC: Add Google Chameleon v3 codec driver Paweł Anikiel
2023-05-08 11:30 ` [PATCH v2 3/7] ASoC: dt-bindings: Add Google Chameleon v3 i2s device Paweł Anikiel
2023-05-08 12:27 ` Rob Herring
2023-05-09 6:14 ` Krzysztof Kozlowski
2023-05-09 6:15 ` Krzysztof Kozlowski
2023-05-08 11:30 ` [PATCH v2 4/7] ASoC: dt-bindings: Add Google Chameleon v3 audio codec Paweł Anikiel
2023-05-08 12:27 ` Rob Herring
2023-05-09 6:18 ` Krzysztof Kozlowski [this message]
2023-05-09 9:54 ` Mark Brown
2023-05-09 10:39 ` Paweł Anikiel
2023-05-08 11:30 ` [PATCH v2 5/7] ARM: dts: chameleonv3: Add mute gpio hog Paweł Anikiel
2023-05-08 11:30 ` [PATCH v2 6/7] ARM: dts: chameleonv3: Add Chameleon v3 audio Paweł Anikiel
2023-05-08 11:30 ` [PATCH v2 7/7] ASoC: ssm2602: Add workaround for playback distortions Paweł Anikiel
2023-05-12 4:19 ` (subset) [PATCH v2 0/7] Add Chameleon v3 ASoC audio Mark Brown
2023-05-18 22:29 ` 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=b8306c55-8551-4c86-f85d-3aebe1ad0ca1@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=amstan@chromium.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=pan@semihalf.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
--cc=upstream@semihalf.com \
/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).