From: Mark Brown <broonie@sirena.org.uk>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Jonathan Cameron <Jonathan.Cameron@gmail.com>,
Eric Miao <eric.y.miao@gmail.com>,
Mike Rapoport <mike@compulab.co.il>,
LKML <linux-kernel@vger.kernel.org>,
Samuel Ortiz <sameo@openedhand.com>,
felipe.balbi@nokia.com, Liam Girdwood <lrg@kernel.org>
Subject: Re: [PATCH 2.6.29-rc1-git4] mfd: da9030 usb charge pump support within mfd driver.
Date: Thu, 15 Jan 2009 18:36:14 +0000 [thread overview]
Message-ID: <20090115183613.GE12768@sirena.org.uk> (raw)
In-Reply-To: <496F3ABF.1020201@cam.ac.uk>
On Thu, Jan 15, 2009 at 01:31:43PM +0000, Jonathan Cameron wrote:
> Mark Brown wrote:
> > Having looked at this problem just this week for some other designs I'm
> > thinking the regulator API might be a good fit for this. It is a supply
> > and the API provides a method to match up the supply with the USB
> > controller (some designs have multiple options there so that's useful).
> > I've not actually tried it yet to see what the pain is like, though.
> I did at one point. The problem here is you aren't simply controlling the
> current / voltage. You are switching it between various automatic modes
> and a manual override. Only in the manually overridden states is it
> much like a regulator and then it's one with very odd properties.
Yes, they're rather different and would require additional APIs for
controlling some of the features, though it may be that we can get away
with doing a lot of the configuration in platform data or board init
code with a more limited subset configured dynamically by the USB stack.
> If these are consistent enough across different pmic's I guess it could
> be blugeoned in, but I'm not convinced this is true.
Yes, that needs to be investigated. I'd hope there's *some* similarity
since at the end of the day it's all USB but I've not got to the point
of looking at that yet.
next prev parent reply other threads:[~2009-01-15 18:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 18:16 Jonathan Cameron
2009-01-15 1:04 ` Eric Miao
2009-01-15 6:34 ` Mike Rapoport
2009-01-15 7:02 ` Eric Miao
2009-01-15 7:28 ` Mike Rapoport
2009-01-15 8:13 ` Eric Miao
2009-01-15 11:22 ` Jonathan Cameron
2009-01-15 13:02 ` Mark Brown
2009-01-15 13:31 ` Jonathan Cameron
2009-01-15 18:36 ` Mark Brown [this message]
2009-01-15 6:38 ` Mike Rapoport
2009-01-15 11:11 ` Jonathan Cameron
2009-01-15 11:23 ` Mike Rapoport
2009-01-15 11:14 ` Jonathan Cameron
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=20090115183613.GE12768@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=Jonathan.Cameron@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=felipe.balbi@nokia.com \
--cc=jic23@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@kernel.org \
--cc=mike@compulab.co.il \
--cc=sameo@openedhand.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
all inboxes | Powered by JetHome®