linux-kernel - Re: [PATCH 2.6.29-rc1-git4] mfd: da9030 usb charge pump support within mfd driver.

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] [day] [month] [year] [list]

Message-ID: <20090115183613.GE12768@sirena.org.uk>
Date:	Thu, 15 Jan 2009 18:36:14 +0000
From:	Mark Brown <broonie@...ena.org.uk>
To:	Jonathan Cameron <jic23@....ac.uk>
Cc:	Jonathan Cameron <Jonathan.Cameron@...il.com>,
	Eric Miao <eric.y.miao@...il.com>,
	Mike Rapoport <mike@...pulab.co.il>,
	LKML <linux-kernel@...r.kernel.org>,
	Samuel Ortiz <sameo@...nedhand.com>, felipe.balbi@...ia.com,
	Liam Girdwood <lrg@...nel.org>
Subject: Re: [PATCH 2.6.29-rc1-git4] mfd: da9030 usb charge pump support within mfd driver.

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