From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>
Subject: [PATCH 0/2] ASoC/regmap: rt5640: Fix resume
Date: Tue, 26 Aug 2014 17:03:11 +0300 [thread overview]
Message-ID: <1409061793-10495-1-git-send-email-jarkko.nikula@linux.intel.com> (raw)
Realtek RT5642 audio codec fails to resume because regmap/regcache tries
to sync consecutive registers using block writes but RT5642 doesn't support
autoincrementing I2C writes according to debugging and oscilloscope
measurments.
I'm not sure is there regression after 75a5f89f635c ("regmap: cache: Write
consecutive registers in a single block write") or was RT564x resume ever
working in mainline so I didn't mark stable yet.
Both patches are independent from each other and can be applied into their
own subsystems separately.
Jarkko Nikula (2):
regmap: cache: Fix regcache_sync_block for non-autoincrementing
devices
ASoC: rt5640: Do not allow regmap to use bulk read-write operations
drivers/base/regmap/regcache.c | 14 +++++++++++++-
sound/soc/codecs/rt5640.c | 1 +
2 files changed, 14 insertions(+), 1 deletion(-)
--
2.1.0
next reply other threads:[~2014-08-26 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 14:03 Jarkko Nikula [this message]
2014-08-26 14:03 ` [PATCH 1/2] regmap: cache: Fix regcache_sync_block for non-autoincrementing devices Jarkko Nikula
2014-08-26 14:21 ` [alsa-devel] " Takashi Iwai
2014-08-27 5:52 ` Jarkko Nikula
2014-08-27 8:18 ` Mark Brown
2014-08-27 11:58 ` Mark Brown
2014-08-26 14:03 ` [PATCH 2/2] ASoC: rt5640: Do not allow regmap to use bulk read-write operations Jarkko Nikula
2014-08-27 12:00 ` 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=1409061793-10495-1-git-send-email-jarkko.nikula@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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