From: Jerome Brunet <jbrunet@baylibre.com>
To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] ASoC: es7134: driver updates
Date: Tue, 3 Jul 2018 17:05:57 +0200 [thread overview]
Message-ID: <20180703150600.17697-1-jbrunet@baylibre.com> (raw)
This patchset fixes issues of v1 [0] around power supply requirement
and add es7154 support.
AVDD is renamed to PVDD to better match the component datasheet.
v1 assumed optional power supplies, which was a wrong thing do.
Now VDD, is required on all chip variant and PVDD is required on the
es7154.
[0]: https://lkml.kernel.org/r/20180629150924.18197-1-jbrunet@baylibre.com
Jerome Brunet (3):
ASoC: es7134: update DT binding with new compatible and supplies
ASoC: es7134: correct required power supplies
ASoC: es7134: add support for the es7154
.../devicetree/bindings/sound/everest,es7134.txt | 7 +-
sound/soc/codecs/es7134.c | 104 ++++++++++++++++++++-
2 files changed, 106 insertions(+), 5 deletions(-)
--
2.14.4
next reply other threads:[~2018-07-03 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 15:05 Jerome Brunet [this message]
2018-07-03 15:05 ` [PATCH v2 1/3] ASoC: es7134: update DT binding with new compatible and supplies Jerome Brunet
2018-07-03 15:34 ` Applied "ASoC: es7134: update DT binding with new compatible and supplies" to the asoc tree Mark Brown
2018-07-03 15:05 ` [PATCH v2 2/3] ASoC: es7134: correct required power supplies Jerome Brunet
2018-07-03 15:34 ` Applied "ASoC: es7134: correct required power supplies" to the asoc tree Mark Brown
2018-07-03 15:06 ` [PATCH v2 3/3] ASoC: es7134: add support for the es7154 Jerome Brunet
2018-07-03 15:33 ` Applied "ASoC: es7134: add support for the es7154" 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=20180703150600.17697-1-jbrunet@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®