From: Jonathan Cameron <jic23@cam.ac.uk>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Jonathan Cameron <Jonathan.Cameron@gmail.com>,
Liam Girdwood <lrg@kernel.org>,
felipe.balbi@nokia.com, eric miao <eric.y.miao@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Regulator RFC] da903x: Where should usb charge pump support go?
Date: Wed, 29 Oct 2008 12:48:41 +0000 [thread overview]
Message-ID: <49085BA9.8050306@cam.ac.uk> (raw)
In-Reply-To: <20081029122705.GA14648@sirena.org.uk>
Mark Brown wrote:
> On Wed, Oct 29, 2008 at 12:18:04PM +0000, Jonathan Cameron wrote:
>
>> ADC
>> Used partly for internal monitoring functionality, partly for
>> auxiliary inputs. The question on this is whether to implement
>> it as a hwmon driver (somewhat unusual form, but sort of fits)
>> or whether some of this is needed for feedback to the battery
>> charger code etc.
>
> For WM8350 this is implemented as a device-specific function in the
> driver core which is then used by other drivers to export the
> information to relevant subsystems.
Seems a sensible option. Can always put a hwmon driver on top of that
if people want the nice userspace interfaces etc.
> There was some work on a generic ADC framework that might be a better
> fit for the auxiliary inputs but I'm not sure where that's going ATM or
> if it's really appropriate.
That's probably me anyway (industrialio), it's stalled whilst I switch
my test platform to this driver and isn't really suitable for this
(unless someone wants to abuse the auxiliary adc inputs for general
purpose stuff).
It's focus (principally) is on fast capture from sensors by triggering events
(periodic timers / gpio / non periodic triggering schedules - haven't done
that one yet) rather than internal monitoring. Other such as input / hwmon
may be built on top of the underlying core, but that's not done yet.
As a quick and dirty progress report, the device handling side of things
is in place and working well. Current work is on generalizing the triggering
framework and working out how to handle the connectivity issues cleanly.
I did promise to post a release at the end of last week but have dropped
back a chunk as some 'minor' changes proved rather complex to do.
Jonathan
next prev parent reply other threads:[~2008-10-29 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 11:18 [Regulator RFC] da903x: Where should usb charge pump support go? Jonathan Cameron
2008-10-28 11:23 ` Felipe Balbi
2008-10-28 12:03 ` Liam Girdwood
2008-10-29 12:18 ` Jonathan Cameron
2008-10-29 12:27 ` Mark Brown
2008-10-29 12:48 ` Jonathan Cameron [this message]
2008-10-29 13:05 ` Mark Brown
2008-10-29 13:21 ` Mike Rapoport
2008-10-28 11:59 ` 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=49085BA9.8050306@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Jonathan.Cameron@gmail.com \
--cc=broonie@sirena.org.uk \
--cc=eric.y.miao@gmail.com \
--cc=felipe.balbi@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@kernel.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