public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Anup Sharma <anupnewsmail@gmail.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
	KCHSU0@nuvoton.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: dt-bindings: nau8540: Convert to dtschema
Date: Fri, 5 May 2023 15:55:58 -0500	[thread overview]
Message-ID: <20230505205558.GA3544888-robh@kernel.org> (raw)
In-Reply-To: <ZE9rK6mktPByvRRz@yoga>

On Mon, May 01, 2023 at 01:02:59PM +0530, Anup Sharma wrote:
> Convert the NAU8540 audio CODEC bindings to DT schema
> 
> Signed-off-by: Anup Sharma <anupnewsmail@gmail.com>
> ---
>  .../devicetree/bindings/sound/nau8540.txt     | 16 --------
>  .../bindings/sound/nuvoton,nau8540.yaml       | 40 +++++++++++++++++++
>  2 files changed, 40 insertions(+), 16 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/sound/nau8540.txt
>  create mode 100644 Documentation/devicetree/bindings/sound/nuvoton,nau8540.yaml
> 
> diff --git a/Documentation/devicetree/bindings/sound/nau8540.txt b/Documentation/devicetree/bindings/sound/nau8540.txt
> deleted file mode 100644
> index 307a76528320..000000000000
> --- a/Documentation/devicetree/bindings/sound/nau8540.txt
> +++ /dev/null
> @@ -1,16 +0,0 @@
> -NAU85L40 audio CODEC
> -
> -This device supports I2C only.
> -
> -Required properties:
> -
> -  - compatible : "nuvoton,nau8540"
> -
> -  - reg : the I2C address of the device.
> -
> -Example:
> -
> -codec: nau8540@1c {
> -       compatible = "nuvoton,nau8540";
> -       reg = <0x1c>;
> -};
> diff --git a/Documentation/devicetree/bindings/sound/nuvoton,nau8540.yaml b/Documentation/devicetree/bindings/sound/nuvoton,nau8540.yaml
> new file mode 100644
> index 000000000000..ac344e435a5c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/nuvoton,nau8540.yaml
> @@ -0,0 +1,40 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/sound/nuvoton,nau8540.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Nuvoton Technology Corporation NAU85L40 Audio CODEC
> +
> +maintainers:
> +  - KCHSU0@nuvoton.com, broonie@kernel.org

Not the right format. It's one email per line/entry.

It needs a name too and drop Mark. It's who knows the h/w, not who 
applies patches.

> +
> +allOf:
> +  - $ref: dai-common.yaml#
> +
> +properties:
> +  compatible:
> +    const: nuvoton,nau8540
> +
> +  reg:
> +    maxItems: 1
> +
> +  "#sound-dai-cells":
> +    const: 0
> +
> +required:
> +  - compatible
> +  - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    i2c {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +        codec@1c {
> +            compatible = "nuvoton,nau8540";
> +            reg = <0x1c>;
> +        };
> +    };
> -- 
> 2.34.1
> 

  reply	other threads:[~2023-05-05 20:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01  7:32 [PATCH] ASoC: dt-bindings: nau8540: Convert to dtschema Anup Sharma
2023-05-05 20:55 ` Rob Herring [this message]
2023-05-09  6:38 ` 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=20230505205558.GA3544888-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=KCHSU0@nuvoton.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=anupnewsmail@gmail.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.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