| 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: <20111217092044.GC2833@opensource.wolfsonmicro.com> Date: Sat, 17 Dec 2011 09:20:44 +0000 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: "Moffett, Kyle D" <Kyle.D.Moffett@...ing.com> Cc: Rob Herring <robherring2@...il.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "devicetree-discuss@...ts.ozlabs.org" <devicetree-discuss@...ts.ozlabs.org>, Liam Girdwood <lrg@...com>, Grant Likely <grant.likely@...retlab.ca> Subject: Re: [REPOST RFC PATCH 0/3] New "gpio-poweroff" driver to turn off platform devices with GPIOs On Wed, Dec 14, 2011 at 02:34:37PM -0600, Moffett, Kyle D wrote: > On Dec 14, 2011, at 07:02, Mark Brown wrote: > > The regulator API in -next has DT bindings. > Based on the description of our hardware, is there a good way that I > can wire up gpio-regulator driver to our hardware with just the device > tree (and maybe one small board-specific function) to make it shut down > each domain in sequence at poweroff time? Otherwise I will just go back > to my custom board-specific function for GPIO-twiddling. No, it's a very rare use case so there's nothing off the shelf. But it should be straightfoward to write a device driver doing this. -- 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