From: "Roman Smrž" <roman@amarulasolutions.com>
To: "Peter Rosin" <peda@lysator.liu.se>,
"Martin Povišer" <povik+lin@cutebit.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Nuno Sá" <nuno.sa@analog.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Shenghao Ding" <shenghao-ding@ti.com>,
"Kevin Lu" <kevin-lu@ti.com>, "Baojun Xu" <baojun.xu@ti.com>,
"Sen Wang" <sen@ti.com>, "Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>
Cc: asahi@lists.linux.dev, linux-sound@vger.kernel.org,
patches@opensource.cirrus.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-amarula@amarulasolutions.com,
"Michael Trimarchi" <michael@amarulasolutions.com>,
"Roman Smrž" <roman@amarulasolutions.com>
Subject: [PATCH v2 1/5] ASoC: dt-bindings: Add ti,pcm1795 and ti,pcm1796
Date: Fri, 16 Oct 2026 12:33:54 +0200 [thread overview]
Message-ID: <20261016-work-v2-1-9340b9555fbb@amarulasolutions.com> (raw)
In-Reply-To: <20261016-work-v2-0-9340b9555fbb@amarulasolutions.com>
From: Michael Trimarchi <michael@amarulasolutions.com>
The PCM1795 and PCM1796 are cost/power-reduced variants of PCM1792A.
Both are register compatible with the PCM1792A, so they belong in the
trivial codec schema.
Signed-off-by: Michael Trimarchi <michael@amarulasolutions.com>
Signed-off-by: Roman Smrž <roman@amarulasolutions.com>
---
Changes in v2:
- Updated description.
---
Documentation/devicetree/bindings/sound/trivial-codec.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/sound/trivial-codec.yaml b/Documentation/devicetree/bindings/sound/trivial-codec.yaml
index 9a35dfb17349..a24a21c855e1 100644
--- a/Documentation/devicetree/bindings/sound/trivial-codec.yaml
+++ b/Documentation/devicetree/bindings/sound/trivial-codec.yaml
@@ -36,6 +36,8 @@ properties:
- sdw3019f836300
- ti,pcm1789
- ti,pcm1792a
+ - ti,pcm1795
+ - ti,pcm1796
- ti,pcm5102a
- wlf,wm8510
- wlf,wm8523
--
2.55.0
next prev parent reply other threads:[~2026-10-16 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 10:33 [PATCH v2 0/5] ASoC: pcm179x: Add support for pcm1795 and pcm1796 Roman Smrž
2026-10-16 10:33 ` Roman Smrž [this message]
2026-10-16 10:33 ` [PATCH v2 2/5] ASoC: pcm179x: Refactor regmap value lookup Roman Smrž
2026-10-16 10:33 ` [PATCH v2 3/5] ASoC: pcm179x: Add left-justified formats for pcm1792a Roman Smrž
2026-10-16 10:33 ` [PATCH v2 4/5] ASoC: pcm179x: Add compatible string for pcm1796 and spi_ids entry Roman Smrž
2026-10-16 10:33 ` [PATCH v2 5/5] ASoC: pcm179x: Add support for pcm1975 Roman Smrž
2026-10-16 10:52 ` sashiko-bot
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=20261016-work-v2-1-9340b9555fbb@amarulasolutions.com \
--to=roman@amarulasolutions.com \
--cc=asahi@lists.linux.dev \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kevin-lu@ti.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=michael@amarulasolutions.com \
--cc=nuno.sa@analog.com \
--cc=patches@opensource.cirrus.com \
--cc=peda@lysator.liu.se \
--cc=perex@perex.cz \
--cc=povik+lin@cutebit.org \
--cc=robh@kernel.org \
--cc=sen@ti.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.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