devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Joerg Schambacher <joerg.hifiberry@gmail.com>
Cc: a-krasser@ti.com, joerg@hifiberry.com,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ASoC: pcm512x: Adds bindings for TAS575x devices
Date: Tue, 12 Sep 2023 10:15:35 -0500	[thread overview]
Message-ID: <20230912151535.GA812148-robh@kernel.org> (raw)
In-Reply-To: <20230907160851.14241-1-joerg.hifiberry@gmail.com>

On Thu, Sep 07, 2023 at 06:08:51PM +0200, Joerg Schambacher wrote:
> The TAS5754/6 power amplifiers use the same pcm512x driver with
> only minor restictions described in the bindings document.
> 
> Signed-off-by: Joerg Schambacher <joerg.hifiberry@gmail.com>
> ---
>  .../devicetree/bindings/sound/pcm512x.txt     | 22 +++++++++++++++----
>  1 file changed, 18 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/sound/pcm512x.txt b/Documentation/devicetree/bindings/sound/pcm512x.txt
> index 3aae3b41bd8e..b16cd0463695 100644
> --- a/Documentation/devicetree/bindings/sound/pcm512x.txt
> +++ b/Documentation/devicetree/bindings/sound/pcm512x.txt
> @@ -1,12 +1,12 @@
> -PCM512x audio CODECs
> +PCM512x and TAS575x audio CODECs/amplifiers
>  
>  These devices support both I2C and SPI (configured with pin strapping
> -on the board).
> +on the board). The TAS575x devices only support I2C.
>  
>  Required properties:
>  
> -  - compatible : One of "ti,pcm5121", "ti,pcm5122", "ti,pcm5141" or
> -                 "ti,pcm5142"
> +  - compatible : One of "ti,pcm5121", "ti,pcm5122", "ti,pcm5141",
> +                 "ti,pcm5142", "ti,tas5754" or "ti,tas5756"
>  
>    - reg : the I2C address of the device for I2C, the chip select
>            number for SPI.
> @@ -25,6 +25,7 @@ Optional properties:
>      through <6>.  The device will be configured for clock input on the
>      given pll-in pin and PLL output on the given pll-out pin.  An
>      external connection from the pll-out pin to the SCLK pin is assumed.
> +    Caution: the TAS-desvices only support gpios 1,2 and 3
>  
>  Examples:
>  
> @@ -50,3 +51,16 @@ Examples:
>  		pll-in = <3>;
>  		pll-out = <6>;
>  	};
> +
> +	tas5756: tas5756@4f {
> +		compatible = "ti,tas5756";

Is there anything new here? Just a different compatible doesn't justify 
another example.

With that dropped,

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2023-09-12 15:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 16:08 [PATCH 1/2] ASoC: pcm512x: Adds bindings for TAS575x devices Joerg Schambacher
2023-09-12 15:15 ` Rob Herring [this message]
2023-09-21 10:30   ` Joerg Schambacher

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=20230912151535.GA812148-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=a-krasser@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joerg.hifiberry@gmail.com \
    --cc=joerg@hifiberry.com \
    --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).