From: Axel Lin <axel.lin@ingics.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: [PATCH 2/2] ASoC: ad193x: Drop .volatile_reg implementation
Date: Tue, 20 Oct 2015 16:56:11 +0800 [thread overview]
Message-ID: <1445331371.25880.3.camel@ingics.com> (raw)
In-Reply-To: <1445331286.25880.1.camel@ingics.com>
adau193x_reg_volatile() always return false.
This seems pointless because current code uses REGCACHE_NONE cache_type
which is supposed to be volatile.
Signed-off-by: Axel Lin <axel.lin@ingics.com>
---
sound/soc/codecs/ad193x.c | 6 ------
1 file changed, 6 deletions(-)
diff --git a/sound/soc/codecs/ad193x.c b/sound/soc/codecs/ad193x.c
index 76d7966..3a3f3f2 100644
--- a/sound/soc/codecs/ad193x.c
+++ b/sound/soc/codecs/ad193x.c
@@ -418,14 +418,8 @@ static struct snd_soc_codec_driver soc_codec_dev_ad193x = {
.num_dapm_routes = ARRAY_SIZE(audio_paths),
};
-static bool adau193x_reg_volatile(struct device *dev, unsigned int reg)
-{
- return false;
-}
-
const struct regmap_config ad193x_regmap_config = {
.max_register = AD193X_NUM_REGS - 1,
- .volatile_reg = adau193x_reg_volatile,
};
EXPORT_SYMBOL_GPL(ad193x_regmap_config);
--
2.1.4
next prev parent reply other threads:[~2015-10-20 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 8:54 [PATCH 1/2] ASoC: ssm2518: Drop .volatile_reg implementation Axel Lin
2015-10-20 8:56 ` Axel Lin [this message]
2015-10-20 9:02 ` [PATCH 2/2] ASoC: ad193x: " Lars-Peter Clausen
2015-10-20 19:32 ` Applied "ASoC: ad193x: Drop .volatile_reg implementation" to the asoc tree Mark Brown
2015-10-20 9:02 ` [PATCH 1/2] ASoC: ssm2518: Drop .volatile_reg implementation Lars-Peter Clausen
2015-10-20 19:32 ` Applied "ASoC: ssm2518: Drop .volatile_reg implementation" 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=1445331371.25880.3.camel@ingics.com \
--to=axel.lin@ingics.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
/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