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]

Message-ID: <20081029130551.GB14648@sirena.org.uk>
Date:	Wed, 29 Oct 2008 13:05:51 +0000
From:	Mark Brown <broonie@...ena.org.uk>
To:	Jonathan Cameron <jic23@....ac.uk>
Cc:	Jonathan Cameron <Jonathan.Cameron@...il.com>,
	Liam Girdwood <lrg@...nel.org>, felipe.balbi@...ia.com,
	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:48:41PM +0000, Jonathan Cameron wrote:
> Mark Brown wrote:

> > 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.

If it's anything like WM8350 you'll end up with multiple things sitting
on top of it.

> 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 

Ah, yes - so it is.

> (unless someone wants to abuse the auxiliary adc inputs for general
> purpose stuff).

My experience suggests that at least some designs will want to do that
but if you go with the internal-only support with multiple clients they
can always write a driver on top of that if/when they need it.
--
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/