From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: dd diasemi <dd.diasemi@gmail.com>
Cc: linux-kernel@vger.kernel.org, Anthony Olech <Anthony.Olech@diasemi.com>
Subject: Re: Linux 3.4-rc2 register mapping and paging on I2C device.
Date: Mon, 30 Apr 2012 22:47:18 +0100 [thread overview]
Message-ID: <20120430214718.GB4414@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAEqHmAstczdi2seTHFE0-jLK9fJaKosHjJyo4AJ7E9UKYBrVsg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
On Mon, Apr 30, 2012 at 06:31:37PM +0100, dd diasemi wrote:
> 3. Update regmap API to enable support for register page switching.
Clearly this is the most sensible option. Open coding this in all the
drivers that need it is going to lead to a lot of duplicated effort.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-30 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 17:31 Linux 3.4-rc2 register mapping and paging on I2C device dd diasemi
2012-04-30 21:47 ` Mark Brown [this message]
2012-05-04 9:35 ` dd diasemi
2012-05-04 10:33 ` Mark Brown
2012-05-04 11:40 ` dd diasemi
2012-05-04 12:14 ` 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=20120430214718.GB4414@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Anthony.Olech@diasemi.com \
--cc=dd.diasemi@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