From: Kirill Marinushkin <k.marinushkin@gmail.com>
To: Padmashree S S <padmashreess2006@gmail.com>
Cc: broonie@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-sound@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
lgirdwood@gmail.com
Subject: Re: [PATCH v3] dt-bindings: sound: Convert pcm3060 to DT Schema
Date: Mon, 30 Mar 2026 07:49:15 +0200 [thread overview]
Message-ID: <b8ca83e9-5a48-032a-96bc-a62990cb61f6@gmail.com> (raw)
In-Reply-To: <20260327121919.603768-1-padmashreess2006@gmail.com>
Hello Padmashree,
overall, your proposed changes look good to me, thank you for taking care of
the DT schema for the pcm3060 driver!
I left a few minor comments below, but i am open for a discussion, if
you think
they are not relevant
On 3/27/26 1:19 PM, Padmashree S S wrote:
> Convert pcm3060 to DT Schema
>
> Signed-off-by: Padmashree S S <padmashreess2006@gmail.com>
> ---
> .../devicetree/bindings/sound/pcm3060.txt | 23 ----------
> .../devicetree/bindings/sound/pcm3060.yaml | 42 +++++++++++++++++++
> 2 files changed, 42 insertions(+), 23 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/sound/pcm3060.txt
> create mode 100644 Documentation/devicetree/bindings/sound/pcm3060.yaml
>
> diff --git a/Documentation/devicetree/bindings/sound/pcm3060.txt b/Documentation/devicetree/bindings/sound/pcm3060.txt
> deleted file mode 100644
> index 97de66932d44..000000000000
> --- a/Documentation/devicetree/bindings/sound/pcm3060.txt
> +++ /dev/null
> @@ -1,23 +0,0 @@
> -PCM3060 audio CODEC
> -
> -This driver supports both I2C and SPI.
> -
> -Required properties:
> -
> -- compatible: "ti,pcm3060"
> -
> -- reg : the I2C address of the device for I2C, the chip select
> - number for SPI.
> -
> -Optional properties:
> -
> -- ti,out-single-ended: "true" if output is single-ended;
> - "false" or not specified if output is differential.
> -
> -Examples:
> -
> - pcm3060: pcm3060@46 {
> - compatible = "ti,pcm3060";
> - reg = <0x46>;
> - ti,out-single-ended = "true";
> - };
> diff --git a/Documentation/devicetree/bindings/sound/pcm3060.yaml b/Documentation/devicetree/bindings/sound/pcm3060.yaml
> new file mode 100644
> index 000000000000..2d920a70bced
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/pcm3060.yaml
> @@ -0,0 +1,42 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/sound/pcm3060.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: PCM3060 audio CODEC
Here, we seem to drop a short description, that this driver supports
I2C and SPI. It's maybe not a big deal, but maybe we could return these
details,
as a `description` property? Let me know what you think
> +
> +maintainers:
> + - Kirill Marinushkin <k.marinushkin@gmail.com>
> +
> +properties:
> + compatible:
> + const: ti,pcm3060
> +
> + reg:
> + maxItems: 1
Here, i notice, that we remove the description of the `reg` property.
It was there originally, and in the 1st version of your patch, but not
in v3.
The description here seems important to me - being a documentation, this
yaml could be more helpful, when it describes the meaning of the properties.
Do you think it would be possible to bring the description back?
> +
> + ti,out-single-ended:
> + type: boolean
> + description: |
> + If present, the output is single-ended.
> + If absent, the output is differential.
> +
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + pcm3060: audio-codec@46 {
> + compatible = "ti,pcm3060";
> + reg = <0x46>;
> + ti,out-single-ended;
> + };
> + };
Best regards,
Kirill
next prev parent reply other threads:[~2026-03-30 5:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 12:19 [PATCH v3] dt-bindings: sound: Convert pcm3060 to DT Schema Padmashree S S
2026-03-27 17:15 ` Mark Brown
2026-03-28 13:50 ` Krzysztof Kozlowski
[not found] ` <CAEjBr-aoOhbtZWdYvq3rQ3q+2SKUEctTXPdYcoS4mJyrPf-Yqw@mail.gmail.com>
2026-03-30 19:09 ` Padmashree S S
2026-03-30 5:49 ` Kirill Marinushkin [this message]
2026-03-30 19:10 ` Padmashree S S
2026-04-14 3:48 ` [PATCH v4] ASoC: dt-bindings: ti,pcm3060: add descriptions and rename binding Padmashree S S
2026-04-14 6:39 ` Krzysztof Kozlowski
2026-04-14 13:22 ` Padmashree S S
2026-04-14 19:16 ` Kirill Marinushkin
2026-04-21 19:32 ` Padmashree S S
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=b8ca83e9-5a48-032a-96bc-a62990cb61f6@gmail.com \
--to=k.marinushkin@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=padmashreess2006@gmail.com \
--cc=robh@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