From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: AB8500 Regulators
Date: Tue, 31 Jul 2012 14:47:16 +0100 [thread overview]
Message-ID: <20120731134716.GL4468@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5017CEE4.5010602@linaro.org>
On Tue, Jul 31, 2012 at 01:26:12PM +0100, Lee Jones wrote:
> On 31/07/12 12:08, Mark Brown wrote:
> >>- I now know how the changing voltage API works
> >> - What I don't know is where we'd call it from to initialise them
> >> - Can we do that from the ab8500 regulator driver's init() or probe()?
> >I'm surprised you've managed to miss the existing interfaces:
> > include/linux/regulator/machine.h
> > Documentation/devicetree/bindings/regulator/regulator.txt
> I saw the interfaces, I just don't know what's the correct thing to
> do. I'm leaving Device Tree for the moment. I'm more concerned about
> addressing the problem in the AB8500 Regulator Driver and it's
> Platform counterpart.
> The only thing of interest that I could see was the regulator_init()
> call-back. Is this what you were alluding to in the first link?
No. apply_uV.
> I guess we're going to have to take a rain-check until I can find
> someone who can translate the documentation for me. I just can't
> seem to find even a small paragraph or such which can provide me
> with enough information to make any decisions.
It does seem that way, yes.
next prev parent reply other threads:[~2012-07-31 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 13:49 AB8500 Regulators Lee Jones
2012-07-30 15:26 ` Mark Brown
2012-07-30 16:32 ` Lee Jones
2012-07-30 17:48 ` Mark Brown
2012-07-31 8:46 ` Lee Jones
2012-07-31 11:08 ` Mark Brown
2012-07-31 12:26 ` Lee Jones
2012-07-31 13:47 ` Mark Brown [this message]
2012-07-31 14:21 ` Lee Jones
2012-07-31 14:28 ` Mark Brown
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=20120731134716.GL4468@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).