All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"tony@atomide.com" <tony@atomide.com>
Subject: Re: [PATCH v2 3/4] arm/dts: Add tps65910 regulator DT data to am335x-evm.dts
Date: Thu, 16 Aug 2012 15:00:56 +0100	[thread overview]
Message-ID: <20120816140056.GK15365@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA13D18@DBDE01.ent.ti.com>

On Thu, Aug 16, 2012 at 01:22:27PM +0000, AnilKumar, Chimata wrote:

> But problem here is single input supply battery/main is not sufficient.

What makes you say this?

> pmic->desc[i].supply_name = info->vin_name;
> with this assignment regulator core searches for exact supply name vcc1 or
> vcc2 etc if there are no matches then it will not register any regulators. 

Why does this mean you need multiple regulators?  A single regulator can
of course supply multiple devices.

WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/4] arm/dts: Add tps65910 regulator DT data to am335x-evm.dts
Date: Thu, 16 Aug 2012 15:00:56 +0100	[thread overview]
Message-ID: <20120816140056.GK15365@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA13D18@DBDE01.ent.ti.com>

On Thu, Aug 16, 2012 at 01:22:27PM +0000, AnilKumar, Chimata wrote:

> But problem here is single input supply battery/main is not sufficient.

What makes you say this?

> pmic->desc[i].supply_name = info->vin_name;
> with this assignment regulator core searches for exact supply name vcc1 or
> vcc2 etc if there are no matches then it will not register any regulators. 

Why does this mean you need multiple regulators?  A single regulator can
of course supply multiple devices.

  reply	other threads:[~2012-08-16 14:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24  6:18 [PATCH v2 0/4] Add AM33XX regulators device tree data AnilKumar Ch
2012-07-24  6:18 ` AnilKumar Ch
2012-07-24  6:18 ` [PATCH v2 1/4] ARM: OMAP2+: AM33XX: Add tps65910 " AnilKumar Ch
2012-07-24  6:18   ` AnilKumar Ch
2012-07-24  6:18 ` [PATCH v2 2/4] ARM: OMAP2+: AM33XX: Add tps65217 " AnilKumar Ch
2012-07-24  6:18   ` AnilKumar Ch
2012-07-24  6:18 ` [PATCH v2 3/4] arm/dts: Add tps65910 regulator DT data to am335x-evm.dts AnilKumar Ch
2012-07-24  6:18   ` AnilKumar Ch
2012-08-14 14:25   ` AnilKumar, Chimata
2012-08-14 14:25     ` AnilKumar, Chimata
2012-08-15 12:53     ` Mark Brown
2012-08-15 12:53       ` Mark Brown
2012-08-15 16:47       ` AnilKumar, Chimata
2012-08-15 16:47         ` AnilKumar, Chimata
2012-08-15 16:54         ` Mark Brown
2012-08-15 16:54           ` Mark Brown
2012-08-16 13:22           ` AnilKumar, Chimata
2012-08-16 13:22             ` AnilKumar, Chimata
2012-08-16 14:00             ` Mark Brown [this message]
2012-08-16 14:00               ` Mark Brown
2012-08-20  6:27               ` AnilKumar, Chimata
2012-08-20  6:27                 ` AnilKumar, Chimata
2012-08-20 20:07                 ` Mark Brown
2012-08-20 20:07                   ` Mark Brown
2012-08-21 10:57                   ` AnilKumar, Chimata
2012-08-21 10:57                     ` AnilKumar, Chimata
2012-08-16 13:25           ` AnilKumar, Chimata
2012-08-16 13:25             ` AnilKumar, Chimata
2012-07-24  6:18 ` [PATCH v2 4/4] arm/dts: Add tps65217 regulator DT data to am335x-bone.dts AnilKumar Ch
2012-07-24  6:18   ` AnilKumar Ch
2012-08-14 14:25 ` [PATCH v2 0/4] Add AM33XX regulators device tree data AnilKumar, Chimata
2012-08-14 14:25   ` AnilKumar, Chimata

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=20120816140056.GK15365@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=anilkumar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.