From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: omap3: regulator_get() failure in ads7846
Date: Tue, 7 Sep 2010 12:56:33 +0100 [thread overview]
Message-ID: <20100907115633.GB25830@sirena.org.uk> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301F6C8381A@dbde02.ent.ti.com>
On Tue, Sep 07, 2010 at 05:16:44PM +0530, Premi, Sanjeev wrote:
> ts->reg = regulator_get(&spi->dev, "vcc");
> This regulator isn't defined for omap3evm. And I suspect - once
> defined - the name will be different than "vcc".
What makes you say this? The names for regulator supplies are defined
in terms of the chip being supplied, not in terms of the board.
> Looking at pointers on how this should be handled.
The best thing to do is to define the mapping for the regulator. You
can work around it by enabling REGULATOR_DUMMY.
next prev parent reply other threads:[~2010-09-07 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 11:46 omap3: regulator_get() failure in ads7846 Premi, Sanjeev
2010-09-07 11:56 ` Mark Brown [this message]
2010-09-07 13:26 ` Premi, Sanjeev
2010-09-07 14:18 ` Mark Brown
2010-09-07 12:16 ` Igor Grinberg
2010-09-07 12:51 ` Mark Brown
2010-09-07 12:53 ` Premi, Sanjeev
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=20100907115633.GB25830@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=premi@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox