From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "sameo@linux.intel.com" <sameo@linux.intel.com>,
"lrg@ti.com" <lrg@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] regulator: tps80031: add regulator driver for tps80031
Date: Tue, 6 Nov 2012 14:03:00 +0530 [thread overview]
Message-ID: <5098CB3C.1080301@nvidia.com> (raw)
In-Reply-To: <20121106081647.GC3283@opensource.wolfsonmicro.com>
On Tuesday 06 November 2012 01:46 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Mon, Nov 05, 2012 at 05:30:02PM +0530, Laxman Dewangan wrote:
>> On Monday 05 November 2012 04:12 PM, Mark Brown wrote:
>
>> I have single dcdc ops for all DCDC VIO, SMPS1 to 3.
>> There is different configuration bit for selecting any DCDC to
>> normal, extended or offset. As this ops are share, I can not change
>> the callbacks.
> You can change your code so that it changes the ops it registers
> depending on the configuration.
I rewrote this using the desc.min_uV and desc.step_uV and table in
another patch which I posted. This parameter get configured based on
these bits value.
I have updated the patch v2.
prev parent reply other threads:[~2012-11-06 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 9:44 [PATCH 0/2] tps80031: Add mfd and regulator driver Laxman Dewangan
2012-11-05 9:44 ` [PATCH 1/2] mfd: add TI TPS80031 mfd core driver Laxman Dewangan
2012-11-05 10:31 ` Mark Brown
2012-11-05 9:44 ` [PATCH 2/2] regulator: tps80031: add regulator driver for tps80031 Laxman Dewangan
2012-11-05 10:42 ` Mark Brown
2012-11-05 12:00 ` Laxman Dewangan
2012-11-06 8:16 ` Mark Brown
2012-11-06 8:33 ` Laxman Dewangan [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=5098CB3C.1080301@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sameo@linux.intel.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