devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: “Ryan <ryan.lee.analog@gmail.com>,
	lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
	tiwai@suse.com, rf@opensource.cirrus.com,
	ckeepax@opensource.cirrus.com,
	pierre-louis.bossart@linux.intel.com, herve.codina@bootlin.com,
	wangweidong.a@awinic.com, james.schulman@cirrus.com,
	ajye_huang@compal.corp-partner.google.com, shumingf@realtek.com,
	povik+lin@cutebit.org, flatmax@flatmax.com,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
	robh+dt@kernel.org, devicetree@vger.kernel.org,
	ryans.lee@analog.com
Subject: Re: [PATCH V2 2/2] ASoC: dt-bindings: max98363: add soundwire amplifier
Date: Sat, 11 Mar 2023 10:10:20 +0100	[thread overview]
Message-ID: <de5d336e-43c4-9016-134c-bf5a0aa18280@linaro.org> (raw)
In-Reply-To: <20230311011409.210014-2-ryan.lee.analog@gmail.com>

On 11/03/2023 02:14, “Ryan wrote:
> From: Ryan Lee <ryans.lee@analog.com>
> 
> This patch adds dt-bindings information for Analog Devices MAX98363
> SoundWire Amplifier.
> 
> Signed-off-by: Ryan Lee <ryans.lee@analog.com>
> ---
> Changes from v1:
>   Fixed a syntax error for the 'dt_binding_check' build.
>   Removed unnecessary properties.
>   Added description about SoundWire device ID of MAX98363
> 
>  .../bindings/sound/adi,max98363.yaml          | 42 +++++++++++++++++++
>  1 file changed, 42 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/sound/adi,max98363.yaml
> 
> diff --git a/Documentation/devicetree/bindings/sound/adi,max98363.yaml b/Documentation/devicetree/bindings/sound/adi,max98363.yaml
> new file mode 100644
> index 000000000000..0e71b6c84007
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/adi,max98363.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/adi,max98363.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Analog Devices MAX98363 SoundWire Amplifier
> +
> +maintainers:
> +  - Ryan Lee <ryans.lee@analog.com>
> +
> +description:
> +  The MAX98363 is a SoundWire input Class D mono amplifier that
> +  supports MIPI SoundWire v1.2-compatible digital interface for
> +  audio and control data.
> +  SoundWire peripheral device ID of MAX98363 is 0x3X019F836300
> +  where X is the peripheral device unique ID decoded from pin.
> +  It supports up to 10 peripheral devices(0x0 to 0x9).
> +
> +properties:
> +  compatible:
> +    enum:
> +      - adi,max98363

Aren't soundwire devices supposed to use device ID as compatible?

Missing blank line

> +  reg:
> +    maxItems: 1
> +    description: Peripheral-device unique ID decoded from pin.
> +

It's not a DAI?

> +required:
> +  - compatible
> +  - reg

Missing blank line

> +additionalProperties: false
> +
> +examples:
> +  - |
> +    soundwire {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +        amplifier@3 {
> +            compatible = "adi,max98363";
> +            reg = <0x3>;

That looks a bit different than regular SoundWire bus. I would argue
that it's not SoundWire at all...


> +        };
> +    };

Best regards,
Krzysztof


  reply	other threads:[~2023-03-11  9:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11  1:14 [PATCH V2 1/2] ASoC: max98363: add soundwire amplifier driver “Ryan
2023-03-11  1:14 ` [PATCH V2 2/2] ASoC: dt-bindings: max98363: add soundwire amplifier “Ryan
2023-03-11  9:10   ` Krzysztof Kozlowski [this message]
2023-03-17 17:22     ` Lee, RyanS
2023-03-13 14:46 ` [PATCH V2 1/2] ASoC: max98363: add soundwire amplifier driver Pierre-Louis Bossart
2023-03-23 17:51   ` Lee, RyanS

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=de5d336e-43c4-9016-134c-bf5a0aa18280@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=ajye_huang@compal.corp-partner.google.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=devicetree@vger.kernel.org \
    --cc=flatmax@flatmax.com \
    --cc=herve.codina@bootlin.com \
    --cc=james.schulman@cirrus.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=povik+lin@cutebit.org \
    --cc=rf@opensource.cirrus.com \
    --cc=robh+dt@kernel.org \
    --cc=ryan.lee.analog@gmail.com \
    --cc=ryans.lee@analog.com \
    --cc=shumingf@realtek.com \
    --cc=tiwai@suse.com \
    --cc=wangweidong.a@awinic.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).