linux-kernel - Re: [Regulator RFC] da903x: Where should usb charge pump support go?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 29 Oct 2008 12:27:23 +0000
From:	Mark Brown <broonie@...ena.org.uk>
To:	Jonathan Cameron <Jonathan.Cameron@...il.com>
Cc:	Liam Girdwood <lrg@...nel.org>, felipe.balbi@...ia.com,
	ext Jonathan Cameron <jic23@....ac.uk>,
	eric miao <eric.y.miao@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [Regulator RFC] da903x: Where should usb charge pump support go?

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.

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/