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: Wed, 15 Aug 2012 13:53:39 +0100 [thread overview]
Message-ID: <20120815125338.GA13544@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA1293E@DBDE01.ent.ti.com>
On Tue, Aug 14, 2012 at 02:25:18PM +0000, AnilKumar, Chimata wrote:
> AM335x EVM have one dedicated input supply which provide supplies to all
> the PMIC regulators. According to tps65910 "VDD1 regulator" input supply
> is from vcc1 so we have to create a dummy/parent/some node to handle this.
> Example below has the details.
Your device tree should accurately reflect the hardware.
> Similarly we have to add 7 more fixed regulators entries to provide input
> supply to different PMIC regulators.
If you have all these unrelated supplies in the system then your device
tree should accurately reflect that. However this would be a very
unusual hardware design. Usually there would be a very small set of
system supply rails, frequently only one.
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: Wed, 15 Aug 2012 13:53:39 +0100 [thread overview]
Message-ID: <20120815125338.GA13544@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA1293E@DBDE01.ent.ti.com>
On Tue, Aug 14, 2012 at 02:25:18PM +0000, AnilKumar, Chimata wrote:
> AM335x EVM have one dedicated input supply which provide supplies to all
> the PMIC regulators. According to tps65910 "VDD1 regulator" input supply
> is from vcc1 so we have to create a dummy/parent/some node to handle this.
> Example below has the details.
Your device tree should accurately reflect the hardware.
> Similarly we have to add 7 more fixed regulators entries to provide input
> supply to different PMIC regulators.
If you have all these unrelated supplies in the system then your device
tree should accurately reflect that. However this would be a very
unusual hardware design. Usually there would be a very small set of
system supply rails, frequently only one.
next prev parent reply other threads:[~2012-08-15 12:53 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 [this message]
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
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=20120815125338.GA13544@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.