From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.com>, Johannes Stezenbach <js@sig21.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/2] ASoC: sta32x: Convert to regmap
Date: Mon, 10 Sep 2012 15:49:54 +0800 [thread overview]
Message-ID: <20120910074952.GD6749@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1347246103-10010-2-git-send-email-broonie@opensource.wolfsonmicro.com>
On Mon, Sep 10, 2012 at 11:01:43AM +0800, Mark Brown wrote:
> Long term all drivers should be using regmap directly. This is more
> idiomatic and moves us towards the removal of the ASoC level cache
> code.
This also needs
.cache_type = REGCACHE_RBTREE
in the regmap config. I've fixed up locally.
next prev parent reply other threads:[~2012-09-10 7:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 3:01 [PATCH 1/2] ASoC: sta32x: Move regulator acquisition to I2C probe Mark Brown
2012-09-10 3:01 ` [PATCH 2/2] ASoC: sta32x: Convert to regmap Mark Brown
2012-09-10 7:49 ` Mark Brown [this message]
2012-09-10 9:10 ` Johannes Stezenbach
2012-09-10 9:00 ` [PATCH 1/2] ASoC: sta32x: Move regulator acquisition to I2C probe Johannes Stezenbach
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=20120910074952.GD6749@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=js@sig21.net \
--cc=lrg@ti.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).