From: ldewangan@nvidia•com (Laxman Dewangan)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/3] ARM: dt: tegra: seaboard: add regulators
Date: Wed, 11 Jul 2012 15:32:01 +0530 [thread overview]
Message-ID: <4FFD4F19.8070404@nvidia.com> (raw)
In-Reply-To: <20120710170112.GK10022@opensource.wolfsonmicro.com>
On Tuesday 10 July 2012 10:31 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Tue, Jul 10, 2012 at 10:23:48PM +0530, Laxman Dewangan wrote:
>
>> Then I will have 2 question:
>> 1. If that pin is connected to battery then what should be entry?
>> vcc1-supply =<>>>;
>> Do we need to register battery supply as fixed (non-gpio based) and
>> then refer here for phandle?
> Use a fixed voltage regulator to represent the battery.
>
>> 2. what about non-dt case? The regulator registration will also fail
>> here because of there is no regulator saying vcc1 in this case. Do
>> we need to register the vcc1 regualtor as fixed, battery supplied
>> regulator in board files so that the ldo's registration will
>> success?
> Same thing, use a fixed voltage regulator.
Understood completely and it is so simple to support vin-supply. Will
implement the same. Thanks for clearing doubts.
prev parent reply other threads:[~2012-07-11 10:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 23:14 [PATCH 1/3] ARM: dt: tegra: seaboard: add regulators Stephen Warren
2012-06-22 23:14 ` [PATCH 2/3] ARM: dt: tegra: ventana: " Stephen Warren
2012-06-22 23:14 ` [PATCH 3/3] ARM: dt: tegra: paz00: " Stephen Warren
2012-06-23 16:35 ` Marc Dietrich
2012-06-24 11:03 ` Mark Brown
2012-06-24 12:01 ` Marc Dietrich
2012-06-24 12:31 ` Mark Brown
2012-06-24 13:27 ` Marc Dietrich
2012-06-25 8:46 ` Mark Brown
2012-06-25 10:45 ` Marc Dietrich
2012-06-25 11:07 ` Thierry Reding
2012-06-26 22:35 ` Stephen Warren
2012-06-26 23:02 ` Mark Brown
2012-06-26 23:16 ` Stephen Warren
2012-06-29 17:32 ` Stephen Warren
2012-06-30 11:45 ` Mark Brown
2012-06-25 6:24 ` [PATCH 1/3] ARM: dt: tegra: seaboard: " Laxman Dewangan
2012-06-25 15:12 ` Stephen Warren
2012-06-25 15:24 ` Laxman Dewangan
2012-06-25 15:36 ` Stephen Warren
2012-06-25 22:26 ` Mark Brown
2012-06-25 23:09 ` Stephen Warren
2012-06-26 6:38 ` Laxman Dewangan
2012-06-26 8:52 ` Mark Brown
2012-07-10 11:59 ` Laxman Dewangan
2012-07-10 13:44 ` Mark Brown
2012-07-10 13:44 ` Laxman Dewangan
2012-07-10 13:53 ` Mark Brown
2012-07-10 15:04 ` Laxman Dewangan
2012-07-10 15:42 ` Mark Brown
2012-07-10 16:39 ` Laxman Dewangan
2012-07-10 16:52 ` Mark Brown
2012-07-10 16:53 ` Laxman Dewangan
2012-07-10 17:01 ` Mark Brown
2012-07-11 10:02 ` 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=4FFD4F19.8070404@nvidia.com \
--to=ldewangan@nvidia$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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