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: <20141112144837.GI3815@sirena.org.uk>
Date:	Wed, 12 Nov 2014 14:48:37 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Thierry Reding <thierry.reding@...il.com>
Cc:	Allen Martin <amartin@...dia.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: Ensure voltages are within the allowed range

On Wed, Nov 12, 2014 at 01:02:04PM +0100, Thierry Reding wrote:

> Perhaps rather than checking that the voltage is within the valid range
> we could at least cover the case where voltage is zero, which is what
> triggered me to write this patch.

Anything which has a voltage of zero is buggy anyway, zero volts is the
off state and should show up as such.  If we don't have a voltage then
the enable should fail.

> Do you have any recommendations to work around this other than adjusting
> the actual voltage to be within the range?

Such regulators need a way of providing a bootsrapping voltage if
they're off when we start I think.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ