From: Laxman Dewangan <ldewangan@nvidia.com>
To: "gg@slimlogic.co.uk" <gg@slimlogic.co.uk>
Cc: Mark Brown <broonie@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"balbi@ti.com" <balbi@ti.com>, Keerthy <a0393675@ti.com>
Subject: Re: [RFC PATCH] regulator: palmas: enable all modes for SMPS10
Date: Fri, 14 Jun 2013 18:04:17 +0530 [thread overview]
Message-ID: <51BB0DC9.3090809@nvidia.com> (raw)
In-Reply-To: <feb8849eb7c84a17fd53da28df0f82e7@slimlogic.co.uk>
On Wednesday 12 June 2013 08:53 PM, gg@slimlogic.co.uk wrote:
> On 2013-06-12 15:51, Mark Brown wrote:
>> On Wed, Jun 12, 2013 at 03:31:09PM +0100, gg@slimlogic.co.uk wrote:
>>> On 2013-06-12 15:14, Mark Brown wrote:
>>>> Yes, that seems like the most obvious thing here as far as I can tell
>>> >from the frankly fragmented and obscure information but given all the
>>>> confusion that seems to exist among the people working on the driver
>>>> it's really not clear if there's something else going on.
>>> What about the case where they are inputs? For bus power?
>> So the current flow can change direction here?
> Just rechecked the data sheet and it looks like that use-case has
> actually been
> removed from more recent data sheets.
>
> So ignore me, yes now it can be modelled by two regulators!
Thanks for concluding on this.
Kishon,
Are you going to send new patch for splitting this regulator or should I
send for this?
This will help on populating dts file what Keerthi is sending and also
to me for the tegra platform.
next prev parent reply other threads:[~2013-06-14 12:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 10:56 [RFC PATCH] regulator: palmas: enable all modes for SMPS10 Kishon Vijay Abraham I
2013-05-30 11:32 ` Mark Brown
2013-05-30 12:54 ` Kishon Vijay Abraham I
2013-06-01 18:42 ` Mark Brown
2013-05-30 13:00 ` Laxman Dewangan
2013-06-01 18:45 ` Mark Brown
2013-06-01 19:03 ` Laxman Dewangan
2013-06-01 21:05 ` Mark Brown
2013-06-04 9:08 ` Kishon Vijay Abraham I
2013-06-04 9:38 ` Mark Brown
2013-06-04 9:43 ` Kishon Vijay Abraham I
2013-06-04 10:05 ` Mark Brown
2013-06-10 9:50 ` Kishon Vijay Abraham I
2013-06-10 10:03 ` Mark Brown
2013-06-10 11:03 ` Kishon Vijay Abraham I
2013-06-10 12:49 ` Mark Brown
2013-06-12 8:42 ` Laxman Dewangan
2013-06-12 14:14 ` Mark Brown
2013-06-12 14:31 ` gg
2013-06-12 14:51 ` Mark Brown
2013-06-12 15:23 ` gg
2013-06-14 12:34 ` Laxman Dewangan [this message]
2013-06-18 8:27 ` Kishon Vijay Abraham I
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=51BB0DC9.3090809@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=a0393675@ti.com \
--cc=balbi@ti.com \
--cc=broonie@kernel.org \
--cc=gg@slimlogic.co.uk \
--cc=kishon@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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