linux-kernel - 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-next>] [day] [month] [year] [list]

Message-Id: <201208060127.57074.heiko@sntech.de>
Date:	Mon, 6 Aug 2012 01:27:56 +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: regulator: Policy for setting current limits

Hi,

I hit a problem when setting a current limit and am not sure whose fault it is 
(i.e. which component to change). Therefore I'd appreciate a pointer in the 
right direction.

After the recent changes the gpio-regulator always selects the minimal value 
to set. The gpio-vbus driver sets it's current limits as 0 - x mA (x = 100, 
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.

So the question is, what is the correct way to handle this:

(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

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/