From: Vincent Knecht <vincent.knecht@mailoo.org>
To: Mark Brown <broonie@kernel.org>
Cc: phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Vincent Knecht <vincent.knecht@mailoo.org>,
Stephan Gerhold <stephan@gerhold.net>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 2/4] ASoC: codecs: tfa989x: Add support for tfa9897
Date: Fri, 28 May 2021 12:50:59 +0200 [thread overview]
Message-ID: <20210528105101.508254-2-vincent.knecht@mailoo.org> (raw)
In-Reply-To: <20210528105101.508254-1-vincent.knecht@mailoo.org>
Add specific init function to poke needed registers & values for this IC
Signed-off-by: Vincent Knecht <vincent.knecht@mailoo.org>
---
sound/soc/codecs/tfa989x.c | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/sound/soc/codecs/tfa989x.c b/sound/soc/codecs/tfa989x.c
index 408e26eee108..6d94865c534b 100644
--- a/sound/soc/codecs/tfa989x.c
+++ b/sound/soc/codecs/tfa989x.c
@@ -44,6 +44,7 @@
#define TFA989X_CURRENTSENSE4 0x49
#define TFA9895_REVISION 0x12
+#define TFA9897_REVISION 0x97
struct tfa989x_rev {
unsigned int rev;
@@ -175,6 +176,29 @@ static const struct tfa989x_rev tfa9895_rev = {
.init = tfa9895_init,
};
+static int tfa9897_init(struct regmap *regmap)
+{
+ int ret;
+
+ /* Reduce slewrate by clearing iddqtestbst to avoid booster damage */
+ ret = regmap_write(regmap, TFA989X_CURRENTSENSE3, 0x0300);
+ if (ret)
+ return ret;
+
+ /* Enable clipping */
+ ret = regmap_clear_bits(regmap, TFA989X_CURRENTSENSE4, 0x1);
+ if (ret)
+ return ret;
+
+ /* Set required TDM configuration */
+ return regmap_write(regmap, 0x14, 0x0);
+}
+
+static const struct tfa989x_rev tfa9897_rev = {
+ .rev = TFA9897_REVISION,
+ .init = tfa9897_init,
+};
+
/*
* Note: At the moment this driver bypasses the "CoolFlux DSP" built into the
* TFA989X amplifiers. Unfortunately, there seems to be absolutely
@@ -280,6 +304,7 @@ static int tfa989x_i2c_probe(struct i2c_client *i2c)
static const struct of_device_id tfa989x_of_match[] = {
{ .compatible = "nxp,tfa9895", .data = &tfa9895_rev },
+ { .compatible = "nxp,tfa9897", .data = &tfa9897_rev },
{ }
};
MODULE_DEVICE_TABLE(of, tfa989x_of_match);
--
2.31.1
next prev parent reply other threads:[~2021-05-28 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 10:50 [PATCH v1 1/4] ASoC: dt-bindings: nxp,tfa989x: Add tfa9897 support Vincent Knecht
2021-05-28 10:50 ` Vincent Knecht [this message]
2021-05-28 11:53 ` [PATCH v1 2/4] ASoC: codecs: tfa989x: Add support for tfa9897 Stephan Gerhold
2021-05-28 10:51 ` [PATCH v1 3/4] ASoC: dt-bindings: nxp,tfa989x: Add vddd-supply property Vincent Knecht
2021-05-28 10:51 ` [PATCH v1 4/4] ASoC: codecs: tfa989x: Add support for optional vddd-supply Vincent Knecht
2021-05-28 11:54 ` Stephan Gerhold
2021-05-28 11:40 ` [PATCH v1 1/4] ASoC: dt-bindings: nxp,tfa989x: Add tfa9897 support Stephan Gerhold
2021-06-02 16:16 ` 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=20210528105101.508254-2-vincent.knecht@mailoo.org \
--to=vincent.knecht@mailoo.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stephan@gerhold.net \
--cc=tiwai@suse.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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®