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: <1203611191.4071.186.camel@localhost.localdomain>
Date:	Thu, 21 Feb 2008 16:26:30 +0000
From:	Liam Girdwood <lg@...nsource.wolfsonmicro.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.arm.linux.org.uk>
Subject: Re: [UPDATED v2][PATCH 0/6] regulator: voltage and current
	regulator framework

On Thu, 2008-02-21 at 08:41 +0000, Russell King - ARM Linux wrote:
> On Wed, Feb 20, 2008 at 05:08:46PM +0000, Liam Girdwood wrote:
> > This patch series provides a generic framework to allow device drivers
> > to control voltage and current regulators on SoC based devices (e.g.
> > phones, gps, media players).
> 
> Note that I'm explicitly avoiding commenting on this as far as PXA3xx
> devices go, until we're further down the road with PM support on that
> SoC.  It's not clear at present whether a generic PMIC framework will
> be suitable for this SoC since it's my understanding from Marvell that
> we need to talk to the PMIC from IRQs-off contexts.
> 
> So don't take my silence as some sort of acceptance of this code; it
> isn't.

I wasn't ;)

It then might be worth adding this functionality at a later stage when
more can be said about PXA3xx PMIC support. We could always have a
version of the _set() functions that are designed to handle this case.

In the mean time this works well on 3 other SoC CPUs.

Liam

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ