From: Marco Felsch <m.felsch@pengutronix.de>
To: robh+dt@kernel.org, KCHSU0@nuvoton.com, broonie@kernel.org,
thomas.fehrenbacher@siedle.de
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
kernel@pengutronix.de
Subject: [alsa-devel] [PATCH 0/3] Add NAU8812 support
Date: Fri, 15 Nov 2019 17:08:16 +0100 [thread overview]
Message-ID: <20191115160819.15557-1-m.felsch@pengutronix.de> (raw)
Hi,
this small series adds the documentation and support for the nau8812
devices. The exisiting nau8810 driver can handle both devices so we only
need to add the dt-bindings and inform the user by adapting the Kconfig
entry.
Futhermore the series adds the support for the aux-port control.
@John Hsu
Please can you verify that register accesses to the aux-port control
bits don't affect the nau8810 devices? I don't have such a device but
the documentations says that those register fields are just '0'ed. So I
assume the nau8810 devices ignore such writes.
Marco Felsch (2):
dt-bindings: ASoC: add nau8812 documentation
ASoC: nau8810: add support for nau8812
Thomas Fehrenbacher (1):
ASoC: nau8810: add aux input control, available on NAU8812
Documentation/devicetree/bindings/sound/nau8810.txt | 2 +-
sound/soc/codecs/Kconfig | 2 +-
sound/soc/codecs/nau8810.c | 9 +++++++++
sound/soc/codecs/nau8810.h | 2 ++
4 files changed, 13 insertions(+), 2 deletions(-)
--
2.20.1
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2019-11-15 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 16:08 Marco Felsch [this message]
2019-11-15 16:08 ` [alsa-devel] [PATCH 1/3] dt-bindings: ASoC: add nau8812 documentation Marco Felsch
2019-12-03 19:27 ` Rob Herring
2019-11-15 16:08 ` [alsa-devel] [PATCH 2/3] ASoC: nau8810: add support for nau8812 Marco Felsch
2019-11-15 16:08 ` [alsa-devel] [PATCH 3/3] ASoC: nau8810: add aux input control, available on NAU8812 Marco Felsch
2019-11-15 16:12 ` Mark Brown
2019-11-15 16:20 ` Marco Felsch
2019-11-15 17:14 ` Mark Brown
2019-11-16 1:43 ` AS50 KCHsu0
2019-11-18 6:46 ` Marco Felsch
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=20191115160819.15557-1-m.felsch@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=KCHSU0@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=thomas.fehrenbacher@siedle.de \
/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).