mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sen Wang <sen@ti.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: <linux-sound@vger.kernel.org>, <broonie@kernel.org>,
	<lgirdwood@gmail.com>, <robh@kernel.org>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
	<perex@perex.cz>, <tiwai@suse.com>, <shenghao-ding@ti.com>,
	<kevin-lu@ti.com>, <baojun.xu@ti.com>, <niranjan.hy@ti.com>,
	<l-badrinarayanan@ti.com>, <devarsht@ti.com>, <v-singh1@ti.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/4] dt-bindings: sound: Add ti,tas675x
Date: Thu, 2 Apr 2026 19:40:38 -0500	[thread overview]
Message-ID: <b35904a2-0913-456f-b89a-f9f45e6a686a@ti.com> (raw)
In-Reply-To: <20260402-funky-lionfish-of-grandeur-fadba6@quoll>

On 4/2/26 02:53, Krzysztof Kozlowski wrote:
> On Wed, Apr 01, 2026 at 05:28:42PM -0500, Sen Wang wrote:
>> Add device tree binding for the Texas Instruments TAS675x family
>> of four-channel Class-D audio amplifiers with integrated DSP.
>>
>> Signed-off-by: Sen Wang <sen@ti.com>
> 

Hi Krzysztof, Thank you for your review.

> Please use subject prefixes matching the subsystem. You can get them for
> example with 'git log --oneline -- DIRECTORY_OR_FILE' on the directory
> your patch is touching. For bindings, the preferred subjects are
> explained here:
> https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters

Understood, ASoC: dt-bindings: Add ti,tas67524. Apologies for the oversight.

> 
>> ---
>>   .../devicetree/bindings/sound/ti,tas675x.yaml | 278 ++++++++++++++++++
> 
> Filename matching compatible, one of them.
> 
>>   1 file changed, 278 insertions(+)
>>   create mode 100644 Documentation/devicetree/bindings/sound/ti,tas675x.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/sound/ti,tas675x.yaml b/Documentation/devicetree/bindings/sound/ti,tas675x.yaml
>> new file mode 100644
>> index 000000000000..23e4cc77b4ae
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/sound/ti,tas675x.yaml
>> @@ -0,0 +1,278 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/sound/ti,tas675x.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Texas Instruments TAS675x Audio Amplifier
>> +
>> +maintainers:
>> +  - Sen Wang <sen@ti.com>
>> +
>> +description: |
> 
> Do not need '|' unless you need to preserve formatting.
> 
>> +  The TAS675x family (TAS6754, TAS67524) are four-channel, digital-input,
> 
> And devices are not compatible?
> 

They're compatible, and I didn't have any differentiators for this 
initial driver. So I should only keep one.
And also rename ti,tas675x.yaml to ti,tas67524.yaml.

>> +  automotive Class-D audio amplifiers with load diagnostics and an integrated
>> +  DSP for audio processing.
>> +
>> +allOf:
>> +  - $ref: dai-common.yaml#
>> +
>> +properties:
>> +  compatible:
>> +    enum:
>> +      - ti,tas6754
>> +      - ti,tas67524
> 
> Keep alphanumerical order (not natural).
> 
>> +
>> +  reg:
>> +    maxItems: 1
>> +
>> +  '#sound-dai-cells':
>> +    const: 1
>> +    description: |
>> +      The device exposes three DAIs, selected by index.
>> +        0 - Standard Audio Path (Playback)
>> +        1 - Low-Latency Playback Path (Playback)
>> +        2 - Sensory Feedback (Capture - Vpredict and Isense)
>> +      By default, all four channels of each DAI are active. Runtime
>> +      reconfiguration is available through DAPM widgets.
>> +
>> +  interrupts:
>> +    maxItems: 1
>> +    description:
>> +      Active-low falling-edge interrupt from the FAULT pin. When provided,
>> +      the driver uses IRQ-driven fault reporting instead of polling.
>> +
>> +  pd-gpios:
> 
> Use names from gpio-consumer-common
> 

Okay

>> +    maxItems: 1
>> +    description:
>> +      GPIO connected to the power-down (PD#) pin, active low. Controls the
>> +      internal digital circuitry power state. When asserted the device enters
>> +      full power-down mode and all register state is lost. Can be omitted if
>> +      PD pin is hardwired or externally controlled.
>> +
>> +  stby-gpios:
>> +    maxItems: 1
>> +    description:
>> +      GPIO connected to the standby (STBY#) pin, active low. Controls the
>> +      analog power stage. When asserted the device enters Deep Sleep mode
>> +      but remains I2C-accessible with registers retained. Can be omitted if
>> +      STBY pin is tied to PD or hardwired.
>> +
>> +  dvdd-supply:
>> +    description:
>> +      Digital logic supply (1.62 V to 3.6 V). All three supply rails must
>> +      be within their recommended operating ranges before the PD pin is
>> +      released.
>> +
>> +  pvdd-supply:
>> +    description:
>> +      Output FET power supply (4.5 V to 19 V). All three supply rails must
>> +      be within their recommended operating ranges before the PD pin is
>> +      released.
>> +
>> +  vbat-supply:
>> +    description:
>> +      Battery supply for the Class-D output stage (4.5 V to 19 V). Optional
>> +      when PVDD and VBAT are connected to the same supply rail. When absent,
>> +      VBAT is assumed hardwired to PVDD.
>> +
>> +  ti,fast-boot:
>> +    type: boolean
>> +    description:
>> +      Skip DC load diagnostic sweep at power-on to reduce boot latency.
>> +      Automatic diagnostics after fault conditions remain enabled. Hardware
>> +      overcurrent protection is always active.
>> +
>> +  ti,audio-slot-no:
>> +    $ref: /schemas/types.yaml#/definitions/uint32
>> +    description:
>> +      TDM slot offset for the standard audio playback path via SDIN1. A value
>> +      of 4 maps to slot 4. If omitted, slot assignment is derived from the
>> +      tx_mask provided via set_tdm_slot(). Without either property, no slot
>> +      mapping is configured.
>> +
>> +  ti,llp-slot-no:
>> +    $ref: /schemas/types.yaml#/definitions/uint32
>> +    description:
>> +      TDM slot offset for the low-latency playback path via SDIN1. If omitted,
>> +      slot assignment is derived from the tx_mask provided via set_tdm_slot().
>> +      Without either property, no slot mapping is configured. Disabled outside
>> +      of LLP mode, and only relevant for TDM formats.
>> +
>> +  ti,vpredict-slot-no:
>> +    $ref: /schemas/types.yaml#/definitions/uint32
>> +    description: |
>> +      In TDM mode, enables Vpredict output and assigns its starting slot;
>> +      four consecutive slots carry Vpredict Ch1-4 on SDOUT1. May coexist
>> +      with ti,isense-slot-no using separate non-overlapping slots.
>> +
>> +      In I2S mode, enables Vpredict output on SDOUT1 (Ch1/Ch2) and SDOUT2
>> +      (Ch3/Ch4). The slot value is unused. Requires a GPIO configured as
>> +      sdout2 for Ch3/Ch4; without it only Ch1/Ch2 are output. Mutually
>> +      exclusive with ti,isense-slot-no; if both are set, Vpredict takes
>> +      priority.
>> +
>> +      Irrelevant in Left-J and Right-J modes.
>> +
>> +  ti,isense-slot-no:
>> +    $ref: /schemas/types.yaml#/definitions/uint32
>> +    description: |
>> +      In TDM mode, enables Isense output and assigns its starting slot;
>> +      four consecutive slots carry Isense Ch1-4 on SDOUT1. May coexist
>> +      with ti,vpredict-slot-no using separate non-overlapping slots.
>> +
>> +      In I2S mode, enables Isense output on SDOUT1 (Ch1/Ch2) and SDOUT2
>> +      (Ch3/Ch4). The slot value is unused. Requires a GPIO configured as
>> +      sdout2 for Ch3/Ch4; without it only Ch1/Ch2 are output. Mutually
>> +      exclusive with ti,vpredict-slot-no; Vpredict takes priority if both
>> +      are set.
>> +
>> +      Irrelevant in Left-J and Right-J modes.
>> +
>> +  ti,gpio1-function:
>> +    $ref: /schemas/types.yaml#/definitions/string
>> +    description: |
> 
> Do not need '|' unless you need to preserve formatting.
> 

Understood, thanks a lot for your review and the tip. Will post a V3.

>> +      Function for the GPIO_1 pin. When omitted, GPIO_1 remains in its
>> +      power-on default state.
> 
> Best regards,
> Krzysztof
> 


  reply	other threads:[~2026-04-03  0:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <message-id-of-your-RFC-cover-letter>
2026-04-01 22:28 ` [PATCH v2 0/4] ASoC: Add TAS675x quad-channel Class-D amplifier driver Sen Wang
2026-04-01 22:28   ` [PATCH v2 1/4] dt-bindings: sound: Add ti,tas675x Sen Wang
2026-04-02  7:53     ` Krzysztof Kozlowski
2026-04-03  0:40       ` Sen Wang [this message]
2026-04-03  7:19         ` Krzysztof Kozlowski
2026-04-04  3:40           ` Sen Wang
2026-04-04  5:20             ` Krzysztof Kozlowski
2026-04-01 22:28   ` [PATCH v2 2/4] ASoC: codecs: Add TAS675x quad-channel audio amplifier driver Sen Wang
2026-04-02  7:54     ` Krzysztof Kozlowski
2026-04-02 17:10     ` Mark Brown
2026-04-03  1:16       ` Sen Wang
2026-04-01 22:28   ` [PATCH v2 3/4] Documentation: sound: Add TAS675x codec mixer controls documentation Sen Wang
2026-04-01 22:28   ` [PATCH v2 4/4] MAINTAINERS: add entry for TAS675x audio amplifier Sen Wang

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=b35904a2-0913-456f-b89a-f9f45e6a686a@ti.com \
    --to=sen@ti.com \
    --cc=baojun.xu@ti.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devarsht@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kevin-lu@ti.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=l-badrinarayanan@ti.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=niranjan.hy@ti.com \
    --cc=perex@perex.cz \
    --cc=robh@kernel.org \
    --cc=shenghao-ding@ti.com \
    --cc=tiwai@suse.com \
    --cc=v-singh1@ti.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

all inboxes | Powered by JetHome®