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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140804144646.GR30458@sirena.org.uk>
Date:	Mon, 4 Aug 2014 15:46:46 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Heiko Stübner <heiko@...ech.de>
Cc:	linus.walleij@...aro.org, addy.ke@...k-chips.com,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: io-domain voltages as regulators?

On Mon, Aug 04, 2014 at 12:18:40AM +0200, Heiko Stübner wrote:

> As this sound like exactly the thing I'm trying to solve, is handling this via 
> a regulator the correct general way?

My first thought is that it seems sensible if it's used as a regulated
supply in a context where just a plain regulator might be used like
MMC/SDIO type things.  If it's only setting logic levels for I/O pins
but isn't something that's being dynamically managed or really visible
to software (it's just a board design thing) then it might not be worth
it but if it might be controlled by changing an external regulator then
using the same API seems like it might be sensible.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ