mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-24 05:04:00 +08:00
151f4e2bdc
Convert the PM documents to ReST, in order to allow them to build with Sphinx. The conversion is actually: - add blank lines and indentation in order to identify paragraphs; - fix tables markups; - add some lists markups; - mark literal blocks; - adjust title markups. At its new index.rst, let's add a :orphan: while this is not linked to the main index.rst file, in order to avoid build warnings. Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Acked-by: Mark Brown <broonie@kernel.org> Acked-by: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
33 lines
868 B
ReStructuredText
33 lines
868 B
ReStructuredText
==========================
|
|
Regulator Driver Interface
|
|
==========================
|
|
|
|
The regulator driver interface is relatively simple and designed to allow
|
|
regulator drivers to register their services with the core framework.
|
|
|
|
|
|
Registration
|
|
============
|
|
|
|
Drivers can register a regulator by calling::
|
|
|
|
struct regulator_dev *regulator_register(struct regulator_desc *regulator_desc,
|
|
const struct regulator_config *config);
|
|
|
|
This will register the regulator's capabilities and operations to the regulator
|
|
core.
|
|
|
|
Regulators can be unregistered by calling::
|
|
|
|
void regulator_unregister(struct regulator_dev *rdev);
|
|
|
|
|
|
Regulator Events
|
|
================
|
|
|
|
Regulators can send events (e.g. overtemperature, undervoltage, etc) to
|
|
consumer drivers by calling::
|
|
|
|
int regulator_notifier_call_chain(struct regulator_dev *rdev,
|
|
unsigned long event, void *data);
|