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: Wed, 15 Aug 2012 17:54:32 +0100 [thread overview]
Message-ID: <20120815165431.GF15365@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA13118@DBDE01.ent.ti.com>
On Wed, Aug 15, 2012 at 04:47:02PM +0000, AnilKumar, Chimata wrote:
> On Wed, Aug 15, 2012 at 18:23:39, Mark Brown wrote:
> > If you have all these unrelated supplies in the system then your device
> > tree should accurately reflect that. However this would be a very
> In that case I have to add all these fixed regulators.
Why? You then immediately go on to say...
> > unusual hardware design. Usually there would be a very small set of
> > system supply rails, frequently only one.
> In case of AM335X-EVM one dedicated supply (5v) feeding to all the input
> supplies (vcc1-7 and vccio) of the regulators.
...that they all map onto the same physical supply?
next prev parent reply other threads:[~2012-08-15 16:54 UTC|newest]
Thread overview: 16+ 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 ` [PATCH v2 1/4] ARM: OMAP2+: AM33XX: Add tps65910 " AnilKumar Ch
2012-07-24 6:18 ` [PATCH v2 2/4] ARM: OMAP2+: AM33XX: Add tps65217 " 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-08-14 14:25 ` AnilKumar, Chimata
2012-08-15 12:53 ` Mark Brown
2012-08-15 16:47 ` AnilKumar, Chimata
2012-08-15 16:54 ` Mark Brown [this message]
2012-08-16 13:22 ` AnilKumar, Chimata
2012-08-16 14:00 ` Mark Brown
2012-08-20 6:27 ` AnilKumar, Chimata
2012-08-20 20:07 ` Mark Brown
2012-08-21 10:57 ` 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-08-14 14:25 ` [PATCH v2 0/4] Add AM33XX regulators device tree data 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=20120815165431.GF15365@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).