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: <CAM4voa=X_rBkSXRHd=oEOnXhgyfSAeD8LmYnsTeQtd-SYKWwPg@mail.gmail.com> Date: Thu, 6 Dec 2012 11:55:11 +0530 From: Abhilash Kesavan <kesavan.abhilash@...il.com> To: devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org, grant.likely@...retlab.ca, lrg@...com, broonie@...nsource.wolfsonmicro.com Cc: Doug Anderson <dianders@...omium.org>, Olof Johansson <olofj@...gle.com>, Thomas Abraham <thomas.abraham@...aro.org> Subject: Regulator suspend state dt question Hi, Max77686 PMIC has dt support and I wanted to specify the suspend state of the regulator via dt. set_suspend_disable and set_suspend_mode call-backs are already implemented in drivers/regulator/max77686.c. 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. Is calling regulator_suspend_prepare from a machine specific file an option ? Kindly provide me with suggestions as to how I may proceed with this. Regards, Abhilash -- 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