From: Mark Brown <broonie@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
lgirdwood@gmail.combroonie@kernel.org, perex@perex.cz,
tiwai@suse.com, ryans.lee@maximintegrated.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
ryan.lee.maxim@gmail.comalsa-devel@alsa-project.org
Subject: Applied "ASoC: max98927: Updated volatile register list" to the asoc tree
Date: Thu, 31 Aug 2017 12:54:57 +0100 [thread overview]
Message-ID: <E1dnO3l-0000nI-Nt@debutante> (raw)
In-Reply-To: <1497910046-3369-3-git-send-email-ryans.lee@maximintegrated.com>
The patch
ASoC: max98927: Updated volatile register list
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
>From 9c1743ebe0da614517a1b94f171924d5fd758df4 Mon Sep 17 00:00:00 2001
From: Ryan Lee <ryans.lee@maximintegrated.com>
Date: Mon, 28 Aug 2017 16:30:55 -0700
Subject: [PATCH] ASoC: max98927: Updated volatile register list
Signed-off-by: Ryan Lee <ryans.lee@maximintegrated.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
sound/soc/codecs/max98927.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/sound/soc/codecs/max98927.c b/sound/soc/codecs/max98927.c
index b5ee29499e16..768e84dbcdf6 100644
--- a/sound/soc/codecs/max98927.c
+++ b/sound/soc/codecs/max98927.c
@@ -495,6 +495,13 @@ static bool max98927_volatile_reg(struct device *dev, unsigned int reg)
{
switch (reg) {
case MAX98927_R0001_INT_RAW1 ... MAX98927_R0009_INT_FLAG3:
+ case MAX98927_R004C_MEAS_ADC_CH0_READ:
+ case MAX98927_R004D_MEAS_ADC_CH1_READ:
+ case MAX98927_R004E_MEAS_ADC_CH2_READ:
+ case MAX98927_R0051_BROWNOUT_STATUS:
+ case MAX98927_R0087_ENV_TRACK_BOOST_VOUT_READ:
+ case MAX98927_R01FF_REV_ID:
+ case MAX98927_R0100_SOFT_RESET:
return true;
default:
return false;
--
2.14.1
next prev parent reply other threads:[~2017-08-31 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 22:07 [PATCH 1/7] staging: max98927: Added TDM support Ryan Lee
2017-06-19 22:07 ` [PATCH 2/7] staging: max98927: Added controls for Envelope tracking Ryan Lee
2017-06-19 22:07 ` [PATCH 3/7] staging: max98927: Updated volatile register list Ryan Lee
2017-08-31 11:54 ` Mark Brown [this message]
2017-06-19 22:07 ` [PATCH 4/7] staging: max98927: Added missing \n to end of dev_err messages Ryan Lee
2017-06-19 22:07 ` [PATCH 5/7] staging: max98927: Removed an obsolete variable Ryan Lee
2017-06-19 22:07 ` [PATCH 6/7] staging: max98927: Modified chip default register values Ryan Lee
2017-08-31 11:54 ` Applied "ASoC: max98927: Modified chip default register values" to the asoc tree Mark Brown
2017-06-19 22:07 ` [PATCH 7/7] staging: max98927: Added PM suspend and resume function Ryan Lee
2017-08-31 11:54 ` Applied "ASoC: max98927: Added PM suspend and resume function" 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=E1dnO3l-0000nI-Nt@debutante \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.combroonie \
/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