linux-kernel - Re: [PATCH 1/1] Add all TWL4030 regulators to Regulator framework

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]

Date:	Thu, 19 Nov 2009 09:04:08 +0200
From:	Juha Keski-Saari <ext-juha.1.keski-saari@...ia.com>
To:	ext Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	"Valentin Eduardo (Nokia-D/Helsinki)" <eduardo.valentin@...ia.com>,
	"sameo@...ux.intel.com" <sameo@...ux.intel.com>,
	"dbrownell@...rs.sourceforge.net" <dbrownell@...rs.sourceforge.net>,
	"tony@...mide.com" <tony@...mide.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"lrg@...mlogic.co.uk" <lrg@...mlogic.co.uk>,
	"Hunter Adrian (Nokia-D/Helsinki)" <adrian.hunter@...ia.com>,
	"amit.kucheria@...durent.com" <amit.kucheria@...durent.com>,
	"dtor@...l.ru" <dtor@...l.ru>,
	"De-Schrijver Peter (Nokia-D/Helsinki)" 
	<Peter.De-Schrijver@...ia.com>,
	"Kristo Tero (Nokia-D/Tampere)" <Tero.Kristo@...ia.com>
Subject: Re: [PATCH 1/1] Add all TWL4030 regulators to Regulator framework

ext Mark Brown wrote:
> On Wed, Nov 18, 2009 at 04:36:09PM +0200, Eduardo Valentin wrote:
> 
>> But maybe these VINT* should be set as always_on in twl4030-regulator driver?
> 
> Can they support any external load at all?  If not then it would make
> sense for the chip driver to at least provide a default set of
> constraints for them rather than forcing all the machine drivers to do
> it manually.

 From the TRM it appears that the max current output values are as follows

VINTANA1 - 30mA
VINTANA2 - 250mA
VINTDIG  - 100mA

Theoretically they may be able to support external load depending on your machine configuration but still I think providing constraints for them in 
the chip driver could be a good idea since the "always-on" limitation is imposed by the chip and not the machine. Without these three supplies the TWL 
does not function properly, if at all. Also worth noting is that the current implementation of RegulatorFW doesn't appear to be able to turn these 
supplies off (comparing TWL register content with framework status).
--
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/