linux-toradex.git/include/linux/regulator/driver.h, branch T20_LinuxImageV2.0Beta1_20121218

regulator: core: support of supply name through desc

2012-08-03T21:04:37+00:00

Add support of providing the supply name through
regualtor descriptor. This help to fill the supply name
in device based on datasheet.
This patch help to develop driver which is align with
mainline.
This change is small set of change in mainline
---------------
commit 69511a452e6dc6b74fe4f3671a51b1b44b9c57e3
Author: Rajendra Nayak 

    regulator: map consumer regulator based on device tree
---------------

Change-Id: Ia3112f29efe4f0e0c9e98f2b7943255b2eae4c49
Signed-off-by: Laxman Dewangan 
Reviewed-on: http://git-master/r/120883

regulator: Refactor supply implementation to work as regular consumers

2011-06-09T18:14:34+00:00

Currently the regulator supply implementation is somewhat complex and
fragile as it doesn't look like standard consumers but is instead a
parallel implementation. This causes issues with locking and reference
counting.

Move the implementation over to using standard consumers to address this.
Rather than only notifying the supply on the first enable/disable we do so
every time the regulator is enabled or disabled, simplifying locking as we
don't need to hold a lock on the consumer we are about to enable.

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

regulator: add set_voltage_time_sel infrastructure

2011-03-26T14:15:06+00:00

This makes it possible to set the stabilization time for voltage
regulators in the same manner as enable_time(). The interface
only supports regulators that implements fixed selectors.

Cc: Bengt Jonsson 
Signed-off-by: Linus Walleij 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: Add initial per-regulator debugfs support

2011-01-12T14:33:05+00:00

We only expose the use and open counts to userspace, providing a tiny
bit of insight into what the API is up to.

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

regulator: Provide a selector based set_voltage_sel() operation

2011-01-12T14:33:04+00:00

Many regulator drivers implement voltage setting by looping through a
table of possible values, normally because the set of available voltages
can't be mapped onto selectors with simple calcuation. Factor out these
loops by providing a variant of set_voltage() which takes a selector rather
than a voltage range as an argument and implementing a loop through the
available selectors in the core.

This is not going to be suitable for use with all devices as when the
regulator voltage can be mapped onto selector values with a simple
calculation the linear scan through the available values will be more
expensive than just doing the calculation, especially for regulators
that provide fine grained voltage control.

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

regulator: Allow drivers to report voltages as selectors

2011-01-12T14:33:01+00:00

Since drivers already have to provide an API for translating selectors
into voltages they may as well just report the selector values directly
to the core API rather than implement the lookup themselves. The old
interface is left in place for now, but may be removed in future.

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

regulator: Copy constraints from regulators when initialising them

2011-01-12T14:33:01+00:00

Currently the regulator API uses the constraints structure passed in to
the core throughout the lifetime of the object. This means that it is not
possible to mark the constraints as __initdata so if the kernel supports
many boards the constraints for all of them are kept around throughout the
lifetime of the system, consuming memory needlessly. By copying constraints
that are actually used we allow the use of __initdata, saving memory when
multiple boards are supported.

This also means the constraints can be const.

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

regulator: Report actual configured voltage to set_voltage()

2011-01-12T14:32:59+00:00

Change the interface used by set_voltage() to report the selected value
to the regulator core in terms of a selector used by list_voltage().
This allows the regulator core to know the voltage that was chosen
without having to do an explict get_voltage(), which would be much more
expensive as it will generally access hardware.

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

regulator: Allow regulators to specify the time taken to ramp on enable

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

Regulators may sometimes take longer to enable than the control operation
used to do so, either because the regulator has ramp rate control used to
limit inrush current or because the control operation is very fast (GPIO
being the most common example of this).  In order to ensure that consumers
do not rely on the regulator before it is enabled provide an enable_time()
operation and have the core delay for that time before returning to the
caller.

This is implemented as a function since the ramp rate may be specified in
voltage per unit time and therefore the time depend on the configuration.
In future it would be desirable to allow the bulk operations to run the
delays for multiple enables in parallel but this is not currently supported.

Signed-off-by: Mark Brown

regulator/driver: be more specific in nanodoc for is_enabled

2009-09-22T12:32:45+00:00

Document the possibility that is_enabled may also return with negative
errorcodes.

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