From: Baojun Xu <baojun.xu@ti.com>
To: <broonie@kernel.org>, <tiwai@suse.de>
Cc: <andriy.shevchenko@linux.intel.com>, <13916275206@139.com>,
<shenghao-ding@ti.com>, <baojun.xu@ti.com>,
<linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<lgirdwood@gmail.com>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<k-yi@ti.com>, <henry.lo@ti.com>, <robinchen@ti.com>,
<will-wang@ti.com>, <jim.shil@goertek.com>,
<toastcheng@google.com>, <chinkaiting@google.com>
Subject: [PATCH v1 1/2] ASoC: dt-bindings: ti,tas2781: Add TAS5832 support
Date: Thu, 26 Feb 2026 15:57:36 +0800 [thread overview]
Message-ID: <20260226075737.405-1-baojun.xu@ti.com> (raw)
TAS5832 is in same family with TAS5827/28/30.
Signed-off-by: Baojun Xu <baojun.xu@ti.com>
---
Documentation/devicetree/bindings/sound/ti,tas2781.yaml | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/sound/ti,tas2781.yaml b/Documentation/devicetree/bindings/sound/ti,tas2781.yaml
index f3a5638f4239..b21466bb0730 100644
--- a/Documentation/devicetree/bindings/sound/ti,tas2781.yaml
+++ b/Documentation/devicetree/bindings/sound/ti,tas2781.yaml
@@ -1,5 +1,5 @@
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
-# Copyright (C) 2022 - 2025 Texas Instruments Incorporated
+# Copyright (C) 2022 - 2026 Texas Instruments Incorporated
%YAML 1.2
---
$id: http://devicetree.org/schemas/sound/ti,tas2781.yaml#
@@ -107,6 +107,9 @@ properties:
ti,tas5830: 65-W Stereo, Digital Input, High Efficiency Closed-Loop
Class-D Amplifier with Class-H Algorithm
+
+ ti,tas5832: 81-W Stereo, Digital Input, High Efficiency Closed-Loop
+ Class-D Amplifier with Class-H Algorithm
oneOf:
- items:
- enum:
@@ -128,6 +131,7 @@ properties:
- ti,tas5827
- ti,tas5828
- ti,tas5830
+ - ti,tas5832
- const: ti,tas2781
- enum:
- ti,tas2781
@@ -264,6 +268,7 @@ allOf:
- ti,tas5827
- ti,tas5828
- ti,tas5830
+ - ti,tas5832
then:
properties:
reg:
--
2.25.1
next reply other threads:[~2026-02-26 7:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 7:57 Baojun Xu [this message]
2026-02-26 7:57 ` [PATCH v1 2/2] ASoC: tas2781: Add tas5832 support Baojun Xu
2026-02-27 10:34 ` Krzysztof Kozlowski
2026-02-27 10:40 ` [EXTERNAL] " Xu, Baojun
2026-02-27 10:46 ` Krzysztof Kozlowski
2026-03-02 8:24 ` Xu, Baojun
2026-03-02 8:58 ` Krzysztof Kozlowski
2026-03-02 9:22 ` Xu, Baojun
2026-03-02 9:27 ` Krzysztof Kozlowski
2026-03-02 9:37 ` Xu, Baojun
2026-03-02 10:07 ` Krzysztof Kozlowski
2026-03-02 9:44 ` andriy.shevchenko
2026-03-02 10:09 ` Krzysztof Kozlowski
2026-03-06 10:08 ` Ding, Shenghao
2026-03-06 10:41 ` Krzysztof Kozlowski
2026-03-17 6:05 ` Ding, Shenghao
2026-03-17 7:06 ` Krzysztof Kozlowski
2026-03-26 2:24 ` Ding, Shenghao
2026-02-27 10:35 ` [PATCH v1 1/2] ASoC: dt-bindings: ti,tas2781: Add TAS5832 support Krzysztof Kozlowski
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=20260226075737.405-1-baojun.xu@ti.com \
--to=baojun.xu@ti.com \
--cc=13916275206@139.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=chinkaiting@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=henry.lo@ti.com \
--cc=jim.shil@goertek.com \
--cc=k-yi@ti.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=robh@kernel.org \
--cc=robinchen@ti.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.de \
--cc=toastcheng@google.com \
--cc=will-wang@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