From: Daniel Beer <daniel.beer@igorinstitute.com>
To: alsa-devel@alsa-project.org, devicetree@vger.kernel.org
Cc: Daniel Beer <daniel.beer@igorinstitute.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>, Andy Liu <andy-liu@ti.com>,
Mark Brown <broonie@kernel.org>,
Derek Simkowiak <derek.simkowiak@igorinstitute.com>
Subject: [PATCH v3 0/2] ASoC: add support for TAS5805M digital amplifier
Date: Sun, 16 Jan 2022 14:58:56 +1300 [thread overview]
Message-ID: <cover.1642298336.git.daniel.beer@igorinstitute.com> (raw)
This pair of patches implements support for the TAS5805M class D audio
amplifier. This driver, and the example configuration in the device-tree
file, were originally based on a 4.19 series kernel and have been
modified slightly from the tested version.
This resubmission differs from v2 as follows:
- The redundant mutex has been removed
- DSP configuration is loaded as a firmware image, rather than
directly from the device-tree
- The volume control returns non-zero when the values have changed, as
required
- Some corrections to device-tree example
Daniel Beer (2):
ASoC: add support for TAS5805M digital amplifier
ASoC: dt-bindings: add bindings for TI TAS5805M.
.../devicetree/bindings/sound/tas5805m.yaml | 56 ++
sound/soc/codecs/Kconfig | 9 +
sound/soc/codecs/Makefile | 2 +
sound/soc/codecs/tas5805m.c | 567 ++++++++++++++++++
4 files changed, 634 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/tas5805m.yaml
create mode 100644 sound/soc/codecs/tas5805m.c
--
2.30.2
next reply other threads:[~2022-01-16 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 1:58 Daniel Beer [this message]
2022-01-16 1:55 ` [PATCH v3 1/2] ASoC: add support for TAS5805M digital amplifier Daniel Beer
2022-01-16 1:56 ` [PATCH v3 2/2] ASoC: dt-bindings: add bindings for TI TAS5805M Daniel Beer
2022-01-25 10:20 ` [PATCH v3 0/2] ASoC: add support for TAS5805M digital amplifier Mark Brown
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=cover.1642298336.git.daniel.beer@igorinstitute.com \
--to=daniel.beer@igorinstitute.com \
--cc=alsa-devel@alsa-project.org \
--cc=andy-liu@ti.com \
--cc=broonie@kernel.org \
--cc=derek.simkowiak@igorinstitute.com \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).