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: <20140225122644.GC25940@sirena.org.uk>
Date:	Tue, 25 Feb 2014 21:26:44 +0900
From:	Mark Brown <broonie@...nel.org>
To:	Markus Pargmann <mpa@...gutronix.de>
Cc:	Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, kernel@...gutronix.de
Subject: Re: [PATCH 2/2] regulator: core: Error on not always_on dummy
 regulators

On Tue, Feb 25, 2014 at 11:03:47AM +0100, Markus Pargmann wrote:
> It does not make sense to have dummy/fixed regulators that are not
> always_on. This patch adds a check in the set_machine_constraints
> function for this case and returns -EINVAL if such a regulator is
> registered.

Such a regulator isn't going to be useful in a system but that doesn't
mean that they shouldn't be registerable since that allows people to
look at their state.  For example a device might have some GPIO managed
regulators where the GPIO is tied low if the regulator isn't in use in
the system.

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