linux-toradex.git/drivers/regulator/dummy.c, branch v3.14.16

regulator: remove use of __devinit

2012-11-20T01:31:26+00:00

CONFIG_HOTPLUG is going away as an option so __devinit is no longer
needed.

Signed-off-by: Bill Pemberton 
Signed-off-by: Mark Brown

regulator: make the dummy regulator's print_constraint more helpful

2012-08-08T13:31:53+00:00

This prevents the output of just

	dummy:

in the boot log. Now it says:

	regulator-dummy: no parameters

which at least doesn't make it look like an accidental printk and also doesn't
only use "dummy" which could mean anything.

Signed-off-by: Uwe Kleine-König 
Signed-off-by: Mark Brown

regulator: dummy: Specify a struct device

2012-05-10T09:48:28+00:00

This will be becoming mandatory.

Signed-off-by: Mark Brown 
Acked-by: Liam Girdwood

regulator: core: Use a struct to pass in regulator runtime configuration

2012-04-09T11:37:09+00:00

Rather than adding new arguments to regulator_register() every time we
want to add a new bit of dynamic information at runtime change the function
to take these via a struct. By doing this we avoid needing to do further
changes like the recent addition of device tree support which required each
regulator driver to be updated to take an additional parameter.

The regulator_desc which should (mostly) be static data is still passed
separately as most drivers are able to configure this statically at build
time.

Signed-off-by: Mark Brown

regulator: pass additional of_node to regulator_register()

2011-11-23T18:47:04+00:00

With device tree support for regulators, its needed that the
regulator_dev->dev device has the right of_node attached.
To be able to do this add an additional parameter to the
regulator_register() api, wherein the dt-adapted driver can
then pass this additional info onto the regulator core.

Signed-off-by: Rajendra Nayak 
Signed-off-by: Mark Brown

regulator: Add export.h for THIS_MODULE to dummy.c

2011-10-31T23:32:15+00:00

So that THIS_MODULE is still in scope once we clean up the presence
of module.h being everywhere.

Signed-off-by: Paul Gortmaker

regulator: Properly register dummy regulator driver

2011-06-08T19:15:34+00:00

Recent changes in the driver core appear to mean that the data structures
for the driver core are not fully initialised unless the driver is bound.
Make sure the driver core knows the dummy driver is in use by binding it
to a driver.

Signed-off-by: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: Provide optional dummy regulator for consumers

2010-03-03T14:49:26+00:00

In order to ease transitions with drivers are boards start using regulators
provide an option to cause all regulator_get() calls to succeed, with a
dummy always on regulator being supplied where one has not been configured.
A warning is printed whenever the dummy regulator is used to aid system
development.

This regulator does not implement any regulator operations but will allow
simple consumers which only do enable() and disable() calls to run. It
is kept separate from the fixed voltage regulator to avoid Kconfig
confusion on the part of users when it is extended to allow boards to
explicitly use the dummy regulator to simplify cases where the majority
of supplies are from fixed regulators without software control.

This option is currently only effective for systems which do not specify
full constriants. If required an override could also be provided to allow
these systems to use the dummy regulator, though it is likely that
unconfigured supplies on such systems will lead to error due to
regulators being powered down more aggressively when not in use.

Signed-off-by: Mark Brown 
Signed-off-by: Liam Girdwood