public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sen Wang <sen@ti.com>
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: Sat, 4 Apr 2026 07:20:40 +0200	[thread overview]
Message-ID: <0b4c3a01-6dbe-49bb-b2d9-f9e2f6677c59@kernel.org> (raw)
In-Reply-To: <0a73ae00-5d57-4701-88dc-9a861d44a2c5@ti.com>

On 04/04/2026 05:40, Sen Wang wrote:
> On 4/3/26 02:19, Krzysztof Kozlowski wrote:
>> On 03/04/2026 02:40, Sen Wang wrote:
>>>>> 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.
>>
>> No, you should express compatibility. See writing bindings, writing
>> schema, example schema docs or DTS101 talk.
>>
> 
> Thank you for clarifying Krzysztof, DTS101 talk is immensely helpful.
> 
> Regarding the compatibles, if I use ti,tas67524 as a fallback:
> 
>    compatible:
>      oneOf:
>        - items:
>          - enum:
>            - ti,tas6754
>          - const: ti,tas67524
>        - const: ti,tas67524
> 
> Does this look correct? I've also seen some bindings use 'enum' even for 
> single values under oneOf, but I'm assuming 'const' is preferred for 
> single entries as advocated in the example schema?

Concept is correct. You have incomplete indentation, but this will be
pointed out by yamllint during dt_binding_check, so be sure that
yamlling and dtschema Python packages are installed.

Best regards,
Krzysztof

  reply	other threads:[~2026-04-04  5:20 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
2026-04-03  7:19         ` Krzysztof Kozlowski
2026-04-04  3:40           ` Sen Wang
2026-04-04  5:20             ` Krzysztof Kozlowski [this message]
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=0b4c3a01-6dbe-49bb-b2d9-f9e2f6677c59@kernel.org \
    --to=krzk@kernel.org \
    --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=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=sen@ti.com \
    --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