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:	Tue, 28 Oct 2008 11:59:09 +0000
From:	Mark Brown <broonie@...ena.org.uk>
To:	Jonathan Cameron <jic23@....ac.uk>
Cc:	eric miao <eric.y.miao@...il.com>, Liam Girdwood <lrg@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [Regulator RFC] da903x: Where should usb charge pump support go?

On Tue, Oct 28, 2008 at 11:18:24AM +0000, Jonathan Cameron wrote:

> The key one for me is control of the USB charge pump. So the question is, does
> this fit within the regulator framework (i.e. should I add it to the regulator
> driver) or should this be a seperate driver (and if so where?)

> Personally I'm not convinced it fits cleanly within the regulator framework
> given it is probably only ever going to get called from one driver and has
> somewhat odd properties!

What exactly does the USB charge pump control do here?  Is it purely
controlling the power supplied to USB (I'm assuming that this is the PXA
USB controller and that the DA903x is so closely tied to it nobody would
use it with another CPU)?  I'm guessing it's a bit more than that and
there's also control over the current that can be drawn from USB by the
system as well as that supplied.
--
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/