From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Jangam <ashish.jangam@kpitcummins.com>
Cc: linux-kernel@vger.kernel.org, Anthony.Olech@diasemi.com
Subject: Re: Regmap group read and write issue for special case of PMIC
Date: Tue, 3 Apr 2012 13:45:06 +0100 [thread overview]
Message-ID: <20120403124505.GG3192@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1333456539.24292.24.camel@dhruva>
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
On Tue, Apr 03, 2012 at 06:05:39PM +0530, Ashish Jangam wrote:
> This special case of DA9052/53 like PMIC needs to be handled in the
> regmap. For this can we, in regmap introduce a new flag and its value
> determines whether to translate internally, the regmap group read and
> write call into a series of single read and write calls Or not?
Yes, a flag for this in the regmap_config seems reasonable.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-04-03 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 12:35 Regmap group read and write issue for special case of PMIC Ashish Jangam
2012-04-03 12:45 ` 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=20120403124505.GG3192@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Anthony.Olech@diasemi.com \
--cc=ashish.jangam@kpitcummins.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;
as well as URLs for NNTP newsgroup(s).