From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Venu Byravarasu <vbyravarasu@nvidia.com>
Cc: Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"myungjoo.ham@samsung.com" <myungjoo.ham@samsung.com>
Subject: Re: [RESEND PATCH 1/2] MFD: MAX77693: add MAX77693 MFD driver
Date: Wed, 14 Mar 2012 17:21:02 +0000 [thread overview]
Message-ID: <20120314172101.GA13393@sirena.org.uk> (raw)
In-Reply-To: <D958900912E20642BCBC71664EFECE3E6DD2912D10@BGMAIL02.nvidia.com>
On Tue, Mar 13, 2012 at 11:22:24AM +0530, Venu Byravarasu wrote:
> > So we decide to use legacy way. As regmap is not yet tested. So we
> > summit the current way and revise it later.
> I was under the impression that regmap is stable now. Can you
> plz let me know, what kind of problems you are seeing with
> regmap? As I'm also planning to upstream a MFD using regmap
> very soon, this information will be useful.
Yes, it should be very stable. Personally my primary development
systems have PMICs which use regmap and most of my work is on regmap
based device so I'll probably notice if there's an issue.
next prev parent reply other threads:[~2012-03-14 17:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 5:28 Chanwoo Choi
2012-03-13 5:35 ` Venu Byravarasu
2012-03-13 5:39 ` Kyungmin Park
2012-03-13 5:52 ` Venu Byravarasu
2012-03-13 7:12 ` Chanwoo Choi
2012-03-13 7:19 ` Venu Byravarasu
2012-03-14 17:21 ` Mark Brown [this message]
2012-03-15 10:13 ` Chanwoo Choi
2012-03-20 1:07 ` [RESEND PATCH v2 " Chanwoo Choi
2012-05-11 14:15 ` Samuel Ortiz
2012-05-11 14:25 ` Kyungmin Park
2012-05-11 14:28 ` Kyungmin Park
2012-05-13 10:07 ` Mark Brown
2012-05-14 5:04 ` Chanwoo Choi
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=20120314172101.GA13393@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=sameo@linux.intel.com \
--cc=vbyravarasu@nvidia.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
all inboxes | Powered by JetHome®