From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: broonie@kernel.org
Cc: lgirdwood@gmail.org, alsa-devel@alsa-project.org,
patches@opensource.wolfsonmicro.com, lee.jones@linaro.org,
sameo@linux.intel.com
Subject: Re: [PATCH 2/3] mfd: wm5102: Mark additional registers as volatile
Date: Fri, 6 Jun 2014 14:07:36 +0100 [thread overview]
Message-ID: <20140606130736.GD19857@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1402058000-5357-2-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On Fri, Jun 06, 2014 at 01:33:19PM +0100, Charles Keepax wrote:
> @@ -1878,6 +1875,9 @@ static bool wm5102_volatile_register(struct device *dev, unsigned int reg)
> switch (reg) {
> case ARIZONA_SOFTWARE_RESET:
> case ARIZONA_DEVICE_REVISION:
> + case ARIZONA_WRITE_SEQUENCER_CTRL_0:
> + case ARIZONA_WRITE_SEQUENCER_CTRL_1:
> + case ARIZONA_WRITE_SEQUENCER_CTRL_2:
> case ARIZONA_OUTPUT_STATUS_1:
Just noticed that we are missing WRITE_SEQUENCER_CTRL_3 here, I
might hold off with this patch until:
mfd: wm5102: Mark register write sequencer control 3 readable
Has made it to a public MFD branch I can rebase onto, then I can
add that in too.
Thanks,
Charles
next prev parent reply other threads:[~2014-06-06 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 12:33 [PATCH 1/3] ASoC: Add SND_SOC_BYTES_EXT control type Charles Keepax
2014-06-06 12:33 ` [PATCH 2/3] mfd: wm5102: Mark additional registers as volatile Charles Keepax
2014-06-06 13:07 ` Charles Keepax [this message]
2014-06-06 12:33 ` [PATCH 3/3] ASoC: wm5102: Add controls to allow shaping of ultrasonic response Charles Keepax
2014-06-17 19:22 ` Lee Jones
2014-06-06 12:48 ` [PATCH 1/3] ASoC: Add SND_SOC_BYTES_EXT control type Lars-Peter Clausen
2014-06-06 12:53 ` Charles Keepax
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=20140606130736.GD19857@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).