| 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
| ||
|
Date: Tue, 7 Aug 2012 01:19:34 +0200 From: Heiko Stübner <heiko@...ech.de> To: Mark Brown <broonie@...nsource.wolfsonmicro.com> Cc: Liam Girdwood <lrg@...com>, linux-kernel@...r.kernel.org, Axel Lin <axel.lin@...il.com> Subject: Re: regulator: Policy for setting current limits Am Montag, 6. August 2012, 13:56:33 schrieb Mark Brown: > On Mon, Aug 06, 2012 at 01:27:56AM +0200, Heiko Stübner wrote: > > 500). Therefore if 500mA are the upper limit but the regulator also > > supports lower values, these lower values always get selected (100mA in > > my case). In contrast pda_power sets the target current as both lower > > and upper limit. > > This isn't good, it means that the regulator has to be able to deliver > exactly the limit requested. > > > (a) let the gpio-regulator select the max current (in contrast to the > > minimum voltage) > > (b) change gpio-vbus to also use the target current as min and max value > > (c) something else > > 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)? Because 4dbd8f63f07a (regulator: gpio-regulator: Set the smallest voltage/current in the specified range) implemented the exact oposite. Thanks Heiko -- 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/
Powered by blists - more mailing lists