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 2/3] ASoC: nau8810: add support for nau8812
Date: Fri, 15 Nov 2019 17:08:18 +0100 [thread overview]
Message-ID: <20191115160819.15557-3-m.felsch@pengutronix.de> (raw)
In-Reply-To: <20191115160819.15557-1-m.felsch@pengutronix.de>
The nau8812 device [1] uses exactly the same register layout as the
nau8810 so there is no need to differentiate those. The only difference
is the output power and an additional aux-port input on the nau8812.
The registers related to the aux-port don't affect the nau8810 in a
negative way. They are just ignored (set to '0').
[1] http://www.nuvoton.com/resource-files/NAU8812DatasheetRev2.7.pdf
Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
---
sound/soc/codecs/Kconfig | 2 +-
sound/soc/codecs/nau8810.c | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig
index 229cc89f8c5a..d13a2e5d0afb 100644
--- a/sound/soc/codecs/Kconfig
+++ b/sound/soc/codecs/Kconfig
@@ -1470,7 +1470,7 @@ config SND_SOC_NAU8540
depends on I2C
config SND_SOC_NAU8810
- tristate "Nuvoton Technology Corporation NAU88C10 CODEC"
+ tristate "Nuvoton Technology Corporation NAU88C10/12 CODEC"
depends on I2C
config SND_SOC_NAU8822
diff --git a/sound/soc/codecs/nau8810.c b/sound/soc/codecs/nau8810.c
index de26758c30a8..a32a4a8d5f50 100644
--- a/sound/soc/codecs/nau8810.c
+++ b/sound/soc/codecs/nau8810.c
@@ -862,6 +862,7 @@ static int nau8810_i2c_probe(struct i2c_client *i2c,
static const struct i2c_device_id nau8810_i2c_id[] = {
{ "nau8810", 0 },
+ { "nau8812", 0 },
{ }
};
MODULE_DEVICE_TABLE(i2c, nau8810_i2c_id);
@@ -869,6 +870,7 @@ MODULE_DEVICE_TABLE(i2c, nau8810_i2c_id);
#ifdef CONFIG_OF
static const struct of_device_id nau8810_of_match[] = {
{ .compatible = "nuvoton,nau8810", },
+ { .compatible = "nuvoton,nau8812", },
{ }
};
MODULE_DEVICE_TABLE(of, nau8810_of_match);
--
2.20.1
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-11-15 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 16:08 [alsa-devel] [PATCH 0/3] Add NAU8812 support Marco Felsch
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 ` Marco Felsch [this message]
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-3-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).