From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] Add ZTE zx-aud96p22 audio codec driver
Date: Thu, 22 Jun 2017 14:51:56 +0800 [thread overview]
Message-ID: <1498114318-32077-1-git-send-email-shawnguo@kernel.org> (raw)
From: Shawn Guo <shawn.guo@linaro.org>
It adds the ASoC driver for zx-aud96p22 audio codec found on ZTE ZX
family SoCs.
Changes for v2:
- Follow document control-names.rst to name controls in a standard way,
so that user space mixer UIs know what to do with them.
- Drop the GPIO support for an optional external amplifier, as it
belongs to machine driver rather than codec driver.
- Support overall power bit with a DAPM supply widget and attach it to
both DAC and ADC components.
- Instead of reset DAC/ADC data path in startup/shutdown hooks, handle
it with DAPM event, so that startup/shutdown hooks get dropped
completely.
Baoyou Xie (2):
ASoC: add bindings for ZTE zx-aud96p22 audio codec
ASoC: zx_aud96p22: add ZTE ZX AUD96P22 codec driver
.../devicetree/bindings/sound/zte,zx-aud96p22.txt | 24 ++
sound/soc/codecs/Kconfig | 5 +
sound/soc/codecs/Makefile | 2 +
sound/soc/codecs/zx_aud96p22.c | 403 +++++++++++++++++++++
4 files changed, 434 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/zte,zx-aud96p22.txt
create mode 100644 sound/soc/codecs/zx_aud96p22.c
--
1.9.1
next reply other threads:[~2017-06-22 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 6:51 Shawn Guo [this message]
2017-06-22 6:51 ` [PATCH v2 1/2] ASoC: add bindings for ZTE zx-aud96p22 audio codec Shawn Guo
2017-06-23 12:04 ` Applied "ASoC: add bindings for ZTE zx-aud96p22 audio codec" to the asoc tree Mark Brown
2017-06-22 6:51 ` [PATCH v2 2/2] ASoC: zx_aud96p22: add ZTE ZX AUD96P22 codec driver Shawn Guo
2017-06-23 12:04 ` Applied "ASoC: zx_aud96p22: add ZTE ZX AUD96P22 codec driver" to the asoc tree 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=1498114318-32077-1-git-send-email-shawnguo@kernel.org \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).