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: <20131217135305.GG3185@sirena.org.uk>
Date:	Tue, 17 Dec 2013 13:53:05 +0000
From:	Mark Brown <broonie@...nel.org>
To:	"Anson.Huang@...escale.com" <Anson.Huang@...escale.com>
Cc:	"lgirdwood@...il.com" <lgirdwood@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] regulator: anatop: add is_enabled interface

On Tue, Dec 17, 2013 at 01:10:12PM +0000, Anson.Huang@...escale.com wrote:

> > In any case I'd be much happier with this patch if it implemented the
> > enable and disable operations as well.

> understand now. then maybe I should remove the PU check in cpufreq,
> although setting PU LDO if it is off before would bring unnessary
> power leak. I will add all these changes together with the dynamic PU
> LDO management feature, thanks for your time!

If you've implemented the enable support correctly then setting the
voltage shouldn't enable the regulator.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ