| 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: Mon, 9 Jan 2012 14:49:36 +0530 From: Laxman Dewangan <ldewangan@...dia.com> To: Mark Brown <broonie@...nsource.wolfsonmicro.com> CC: Laxman Dewangan <ldewangan.com@...dia.com>, "lrg@...mlogic.co.uk" <lrg@...mlogic.co.uk>, "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org> Subject: RE: [PATCH V1] TPS62360: Add tps62360 regulator driver > On Monday, January 09, 2012 2:19 PM, Mark Brown wrote > > > On Monday, January 09, 2012 1:09 PM, Mark Brown wrote > > If valid gpios will be passed then driver will use the LRU mechanism > > for getting desired configuration register for configuring the desired > > voltage (passed through the regulator_setvoltage())and set the gpios > > accordingly through gpio libs. > > In this approach, because we need to set two different gpios for > > desired logic, the output will not go in proper transition from > > current to new one, for some time when we completed setting of > > one gpio and setting second gpio. > > Isn't that an issue anyway? If device is designed like this then I think this will not be an issue. I am happy that I understand the design and in sync with you. I will send the patch with having this change. Thanks you very much for clearing and helping me on understanding and design. -- 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