From: Rob Herring <robh@kernel.org>
To: Bragatheswaran Manickavel <bragathemanick0908@gmail.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: dt-bindings: rt5616: Convert to dtschema
Date: Thu, 28 Sep 2023 11:19:31 -0500 [thread overview]
Message-ID: <20230928161931.GA713974-robh@kernel.org> (raw)
In-Reply-To: <20230925165715.34883-1-bragathemanick0908@gmail.com>
On Mon, Sep 25, 2023 at 10:27:15PM +0530, Bragatheswaran Manickavel wrote:
> Convert the rt5616 audio CODEC bindings to DT schema
> No error/warning seen when running make dt_binding_check
No need to say that. That's the assumption and it should never get
applied if not.
>
> Signed-off-by: Bragatheswaran Manickavel <bragathemanick0908@gmail.com>
> ---
> .../bindings/sound/realtek,rt5616.yaml | 53 +++++++++++++++++++
> .../devicetree/bindings/sound/rt5616.txt | 32 -----------
> 2 files changed, 53 insertions(+), 32 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/sound/realtek,rt5616.yaml
> delete mode 100644 Documentation/devicetree/bindings/sound/rt5616.txt
>
> diff --git a/Documentation/devicetree/bindings/sound/realtek,rt5616.yaml b/Documentation/devicetree/bindings/sound/realtek,rt5616.yaml
> new file mode 100644
> index 000000000000..00ff9b4e3c7e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/realtek,rt5616.yaml
> @@ -0,0 +1,53 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/sound/realtek,rt5616.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Realtek rt5616 ALSA SoC audio codec driver
> +
> +description: |
> + Pins on the device (for linking into audio routes) for RT5616:
> +
> + * IN1P
> + * IN2P
> + * IN2N
> + * LOUTL
> + * LOUTR
> + * HPOL
> + * HPOR
> +
> +maintainers:
> + - Bard Liao <bardliao@realtek.com>
> +
> +allOf:
> + - $ref: dai-common.yaml#
> +
> +properties:
> + compatible:
> + const: realtek,rt5616
> +
> + reg:
> + maxItems: 1
> +
> + "#sound-dai-cells":
> + const: 0
> +
> +required:
> + - compatible
> + - reg
> + - '#sound-dai-cells'
This was not in the original doc. Was that an error? If so, just state
that in the commit msg.
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
blank line
> + codec@1b {
audio-codec@1b
> + compatible = "realtek,rt5616";
> + reg = <0x1b>;
> + #sound-dai-cells = <0>;
> + };
> + };
next prev parent reply other threads:[~2023-09-28 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 16:57 [PATCH] ASoC: dt-bindings: rt5616: Convert to dtschema Bragatheswaran Manickavel
2023-09-28 16:19 ` Rob Herring [this message]
2023-09-29 9:12 ` Bragatheswaran Manickavel
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=20230928161931.GA713974-robh@kernel.org \
--to=robh@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bragathemanick0908@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.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).