From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Marc Reilly <marc@cpdesign.com.au>,
sameo@linux.intel.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
u.kleine-koenig@pengutronix.de,
spi-devel-general@lists.sourceforge.net, oskar@scara.com
Subject: Re: mfd: mc13xxx: add I2C support, V2
Date: Mon, 12 Mar 2012 14:06:20 +0000 [thread overview]
Message-ID: <20120312140620.GB14020@sirena.org.uk> (raw)
In-Reply-To: <20120311115018.GA16825@pengutronix.de>
On Sun, Mar 11, 2012 at 12:50:18PM +0100, Wolfram Sang wrote:
> free, if this is desired. I think the regmap approach should have been tried
> before we go custom. sound/soc/codecs/ad193x.c might give an impression how
> regmap spi/i2c in one driver could look like.
There's a bunch of other examples in sound/soc and also the wm831x PMIC
driver in drivers/mfd. For an initial conversion I'd not worry about
the cache, especially with some of the older PMICs hardware designers
were known to come up with some "innovative usability solutions" which
can cause hassle.
prev parent reply other threads:[~2012-03-12 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 1:29 Marc Reilly
2012-03-11 1:30 ` [PATCH v2 1/3] mfd: mc13xxx-core: Prepare for separate spi and i2c backends Marc Reilly
2012-03-11 9:33 ` Uwe Kleine-König
2012-03-11 1:30 ` [PATCH v2 2/3] mfd: mc13xxx-core: Move spi specific code into separate module Marc Reilly
2012-03-11 1:30 ` [PATCH v2 3/3] mfd: mc13xxx-core: Add i2c driver Marc Reilly
2012-03-11 11:50 ` mfd: mc13xxx: add I2C support, V2 Wolfram Sang
2012-03-12 14:06 ` Mark Brown [this message]
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=20120312140620.GB14020@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@cpdesign.com.au \
--cc=oskar@scara.com \
--cc=sameo@linux.intel.com \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=u.kleine-koenig@pengutronix.de \
--cc=w.sang@pengutronix.de \
/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
all inboxes | Powered by JetHome®