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: Mon, 20 Aug 2012 21:07:15 +0100 [thread overview]
Message-ID: <20120820200715.GT26991@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA19A81@DBDE01.ent.ti.com>
On Mon, Aug 20, 2012 at 06:27:01AM +0000, AnilKumar, Chimata wrote:
> On Thu, Aug 16, 2012 at 19:30:56, Mark Brown wrote:
> > Why does this mean you need multiple regulators? A single regulator can
> > of course supply multiple devices.
> I got your point but tps65910 driver is failing if we add single fixed
> regulator. Solution is driver needs to change or add multiple fixed
> regulators.
No, really. One regulator can supply many things, not being a.
> vrtc:
> tps65910 0-002d: Failed to find supply vcc7
> tps65910 0-002d: failed to register tps65910-pmic regulator
So you've specified a whole bunch of supplies and this one individual
supply is not matching (and it's not the first...). You should
investigate what's gone wrong there rather than bodging around the
problem. I can't immediately say anything much based on the information
you've given.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120820/4e98778b/attachment.sig>
next prev parent reply other threads:[~2012-08-20 20:07 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
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 [this message]
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=20120820200715.GT26991@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).