| 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
| ||
|
Message-ID: <20121210143141.GG6103@opensource.wolfsonmicro.com> Date: Mon, 10 Dec 2012 23:31:42 +0900 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: Lee Jones <lee.jones@...aro.org> Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, arnd@...db.de, linus.walleij@...ricsson.com, ulf.hansson@...aro.org Subject: Re: [PATCH 01/12] regulator: gpio-regulator: Demote GPIO Regulator driver to start later On Mon, Dec 10, 2012 at 02:28:36PM +0000, Lee Jones wrote: > On Mon, 10 Dec 2012, Mark Brown wrote: > > This really isn't a good solution, especially not for a system that's DT > > based - on a DT system we can tell if there should be a GPIO present so > > we should be able to defer only when there's something that might > > provide the GPIO later on. > Understood, but what's the solution for non-DT systems? Provide a fixed regulator or something, perhaps we need a "definitely does not exist" regulator to help with this. For every board you help with a sequencing bodge you're probably going to break another that needs different sequencing; for that matter it's not like GPIO controlled regulators are exclusively used for MMC, or that MMC exclusively uses GPIO - doing this for only one regulator is a bit of a red flag. -- 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