From: Kevin Cernekee <cernekee@chromium.org>
To: lgirdwood@gmail.com, broonie@kernel.org
Cc: lars@metafoo.de, dgreid@chromium.org, abrestic@chromium.org,
olofj@chromium.org, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH V2 0/4] tas571x amplifier driver
Date: Fri, 24 Apr 2015 15:36:44 -0700 [thread overview]
Message-ID: <1429915008-22015-1-git-send-email-cernekee@chromium.org> (raw)
V1->V2:
- Incorporate changes from review feedback
- Change GPIOs to active low
- Create a tas571x_chip struct to capture the growing list of differences
between 5711 and 5717/5719
- Add register defaults for each chip
- Extend regcache_sync_region() to allow it to sync with hardware registers
that don't contain their power-on-reset values
Kevin Cernekee (4):
regmap: cache: Add "was_reset" argument to regcache_sync_region()
ASoC: tas571x: Add DT binding document
ASoC: tas571x: New driver for TI TAS571x power amplifiers
MAINTAINERS: Add entry for tas571x ASoC codec driver
.../devicetree/bindings/sound/tas571x.txt | 41 ++
MAINTAINERS | 6 +
drivers/base/regmap/internal.h | 5 +-
drivers/base/regmap/regcache-lzo.c | 2 +-
drivers/base/regmap/regcache-rbtree.c | 5 +-
drivers/base/regmap/regcache.c | 75 +--
drivers/media/radio/radio-si476x.c | 18 +-
drivers/mfd/wm8994-core.c | 5 +-
include/linux/regmap.h | 4 +-
include/sound/hda_regmap.h | 3 +-
sound/soc/codecs/Kconfig | 5 +
sound/soc/codecs/Makefile | 2 +
sound/soc/codecs/tas571x.c | 521 +++++++++++++++++++++
sound/soc/codecs/tas571x.h | 33 ++
sound/soc/codecs/wm8962.c | 3 +-
15 files changed, 680 insertions(+), 48 deletions(-)
create mode 100644 Documentation/devicetree/bindings/sound/tas571x.txt
create mode 100644 sound/soc/codecs/tas571x.c
create mode 100644 sound/soc/codecs/tas571x.h
--
2.2.0.rc0.207.ga3a616c
next reply other threads:[~2015-04-24 22:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 22:36 Kevin Cernekee [this message]
2015-04-24 22:36 ` [PATCH V2 1/4] regmap: cache: Add "was_reset" argument to regcache_sync_region() Kevin Cernekee
2015-04-25 2:44 ` Kevin Cernekee
2015-04-25 11:27 ` Lars-Peter Clausen
2015-04-25 11:32 ` Mark Brown
2015-04-29 4:58 ` Kevin Cernekee
[not found] ` <CAJzqFtYkSds+s2HA3uKrMQes+D2K1TxOdzm5jJhtt2iZvyqxCA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-29 10:40 ` Mark Brown
2015-04-29 14:13 ` Kevin Cernekee
2015-04-29 16:46 ` Mark Brown
2015-04-29 17:02 ` Kevin Cernekee
2015-04-29 17:34 ` Mark Brown
2015-04-24 22:36 ` [PATCH V2 2/4] ASoC: tas571x: Add DT binding document Kevin Cernekee
[not found] ` <1429915008-22015-1-git-send-email-cernekee-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2015-04-24 22:36 ` [PATCH V2 3/4] ASoC: tas571x: New driver for TI TAS571x power amplifiers Kevin Cernekee
2015-04-25 11:35 ` Mark Brown
2015-04-24 22:36 ` [PATCH V2 4/4] MAINTAINERS: Add entry for tas571x ASoC codec driver Kevin Cernekee
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=1429915008-22015-1-git-send-email-cernekee@chromium.org \
--to=cernekee@chromium.org \
--cc=abrestic@chromium.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dgreid@chromium.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olofj@chromium.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).