From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Add ZTE ZTE zx-aud96p22 audio codec driver
Date: Sat, 17 Jun 2017 22:09:32 +0800 [thread overview]
Message-ID: <1497708574-22380-1-git-send-email-shawnguo@kernel.org> (raw)
From: Shawn Guo <shawn.guo@linaro.org>
This is a pick-up of Baoyou's zx-aud96p22 audio codec driver
submission [1], with quite some significant rework as below.
- Instead of hard-coding the GPIO used to control external amplifier,
use generic devm_gpiod_get_optional() call to retrieve the GPIO
defined in device tree.
- Rather than directly using I2C bus calls, use REGMAP_I2C interface
which is more common for accessing codec register via I2C bus.
- Use snd_kcontrol_new infrastructural for Volume and Mute control.
- Use DAPM widget and route for various power bits control.
- A lot of code cleanups
[1] https://lkml.org/lkml/2017/2/15/170
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 | 28 ++
sound/soc/codecs/Kconfig | 5 +
sound/soc/codecs/Makefile | 2 +
sound/soc/codecs/zx_aud96p22.c | 425 +++++++++++++++++++++
4 files changed, 460 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-17 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 14:09 Shawn Guo [this message]
2017-06-17 14:09 ` [PATCH 1/2] ASoC: add bindings for ZTE zx-aud96p22 audio codec Shawn Guo
2017-06-19 16:16 ` Mark Brown
2017-06-20 3:11 ` Shawn Guo
2017-06-20 14:33 ` Mark Brown
2017-06-21 13:22 ` Shawn Guo
2017-06-17 14:09 ` [PATCH 2/2] ASoC: zx_aud96p22: add ZTE ZX AUD96P22 codec driver Shawn Guo
2017-06-19 16:19 ` Mark Brown
2017-06-20 3:19 ` Shawn Guo
2017-06-20 12:40 ` Mark Brown
2017-06-21 16:03 ` Shawn Guo
2017-06-21 16:13 ` 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=1497708574-22380-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).