| 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: <b90c0690907300520t1dfbd722j73417b1beb6992bc@mail.gmail.com> Date: Thu, 30 Jul 2009 15:20:24 +0300 From: Roger Quadros <quadros.roger@...il.com> To: broonie@...nsource.wolfsonmicro.com Cc: lrg@...mlogic.co.uk, linux-kernel@...r.kernel.org Subject: regulator: adding enable control to fixed regulator interface hi Mark, I have the following use-case scenario for a fixed voltage regulator. Supply ----->| Regulator |-------> Peripheral ^ EN | GPIO ------------- The regulator's enable pin is controlled by a GPIO of the CPU. What is the best way to implement this within the regulator framework? Writing a regulator driver is one solution but I'm sure there must be many instances like this and writing a driver for each case is not that nice. I want to use the fixed regulator driver but this does not have regulator enable/disable control. Isn't it a good idea to have enable/disable control for the current implementation of the fixed voltage regulator i.e. drivers/regulator/fixed.c ? The regulator enabling/disabling functionality can be implemented by platform code and the required function pointers could be passed through fixed_voltage_config structure. If this looks OK, I can send you a patch to implement this functionality. cheers, -roger -- 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