linux-kernel - Re: regulator: Policy for setting current limits

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: <20120807170626.GZ16861@opensource.wolfsonmicro.com>
Date:	Tue, 7 Aug 2012 18:06:26 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Heiko Stübner <heiko@...ech.de>
Cc:	Liam Girdwood <lrg@...com>, linux-kernel@...r.kernel.org,
	Axel Lin <axel.lin@...il.com>
Subject: Re: regulator: Policy for setting current limits

On Tue, Aug 07, 2012 at 01:19:34AM +0200, Heiko Stübner wrote:
> Am Montag, 6. August 2012, 13:56:33 schrieb Mark Brown:

> > Regulators should be tending to the maximum in the available range and
> > consumers should specify the widest range possible so both a and b.

> Is this true for all regulators (i.e. voltage and currency regulators)?

No, voltage regualtors should tend to the lowest voltage.
--
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/