blob: b17e5833ce214f963ed9af87f6f7fcf0e2c5ac18 [file] [log] [blame]
Liam Girdwoode8695eb2008-04-30 17:20:11 +01001Regulator Driver Interface
2==========================
3
4The regulator driver interface is relatively simple and designed to allow
5regulator drivers to register their services with the core framework.
6
7
8Registration
9============
10
11Drivers can register a regulator by calling :-
12
Linus Walleij040932c2009-08-21 14:00:57 +020013struct regulator_dev *regulator_register(struct regulator_desc *regulator_desc,
Axel Lin127ef622012-04-13 15:32:05 +080014 const struct regulator_config *config);
Liam Girdwoode8695eb2008-04-30 17:20:11 +010015
Geert Uytterhoeven3a4c6952014-08-25 10:47:51 +020016This will register the regulator's capabilities and operations to the regulator
Liam Girdwooda5766f12008-10-10 13:22:20 +010017core.
Liam Girdwoode8695eb2008-04-30 17:20:11 +010018
19Regulators can be unregistered by calling :-
20
21void regulator_unregister(struct regulator_dev *rdev);
22
23
24Regulator Events
25================
Geert Uytterhoeven3a4c6952014-08-25 10:47:51 +020026Regulators can send events (e.g. overtemperature, undervoltage, etc) to
27consumer drivers by calling :-
Liam Girdwoode8695eb2008-04-30 17:20:11 +010028
29int regulator_notifier_call_chain(struct regulator_dev *rdev,
30 unsigned long event, void *data);