| 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: Thu, 6 Dec 2012 15:28:38 +0900 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: Abhilash Kesavan <kesavan.abhilash@...il.com> Cc: devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org, grant.likely@...retlab.ca, lrg@...com, Doug Anderson <dianders@...omium.org>, Olof Johansson <olofj@...gle.com>, Thomas Abraham <thomas.abraham@...aro.org> Subject: Re: Regulator suspend state dt question On Thu, Dec 06, 2012 at 11:55:11AM +0530, Abhilash Kesavan wrote: > As of now there is no support in the regulator core to specify the suspend state > (mode, enabled/disabled) using dt. I can add new properties specifying > the intial_state, > mode, enable/disable but I am not too sure if it is appropriate to add > such bindings to > the device tree as they are not actually describing the hardware. Well, it does depend on the hardware a bit - some hardware is hard wired to only have one possible suspend state due to power up requirements. But for a lot of hardware it's flexible... > Is calling regulator_suspend_prepare from a machine specific file an option ? This is not really relevant, it's an orthogonal thing about when we trigger the state transition in the regulator. It's not clear what a good solution is here, sorry. -- 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