linux-toradex.git/include/linux/regulator, branch v2.6.38.6

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: Add API to re-apply voltage to hardware

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

When cooperating with an external control source the regulator setup
may be changed underneath the API. Currently consumers can just redo
the regulator_set_voltage() to restore a previously set configuration
but provide an explicit API for doing this as optimsations in the
regulator_set_voltage() implementation will shortly prevent that.

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

regulators: Moved define for number of regulators in ab8500

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

The define for number of regulators is moved from ab8500-core to
ab8500-regulator so that the regulator driver can be updated
independently of ab8500-core. This also changes the platform
configuration structure of ab8500-core so that it contains a
pointer to the regulator_init_data array plus number of
regulators instead of an fixed size array of pointers to
regulator_init_data.

Signed-off-by: Bengt Jonsson 
Acked-by: Linus Walleij 
Acked-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: Add option for machine drivers to enable the dummy regulator

2010-10-28T21:40:31+00:00

Allow machine drivers to explicitly enable the use of the dummy regulator,
enabling simpler support for systems with only a few specific supplies
visible to software.

It is strongly recommended that this is not used on systems with
substantial software control over their PMICs, for maximum functionality
constrints should be as fully specified as possible.

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

Regulator: LP3972 PMIC regulator driver

2010-10-28T21:40:31+00:00

This patch adds regulator drivers for National Semiconductors LP3972 PMIC.
This LP3972 PMIC controller has 3 DC/DC voltage converters and 5 low drop-out
(LDO) regulators. LP3972 PMIC controller uses I2C interface.

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

MAX8952 PMIC Driver Initial Release

2010-10-28T21:40:31+00:00

MAX8952 PMIC is used to provide voltage output between 770mV - 1400mV
with DVS support. In this initial release, users can set voltages for
four DVS modes, RAMP delay values, and SYNC frequency.
Controlling FPWM/SYNC_MODE/Pull-Down/Ramp Modes and reading CHIP_ID
is not supported in this release.

If GPIO of EN is not valid in platform data, the driver assumes that it
is always-on. If GPIO of VID0 or VID1 is invalid, the driver pulls down
VID0 and VID1 to fix DVS mode as 0 and disables DVS support.

We assume that V_OUT is capable to provide every voltage from 770mV to
1.40V in 10mV steps although the data sheet has some ambiguity on it.

Signed-off-by: MyungJoo Ham 
Signed-off-by: Kyungmin Park 
Acked-by: Mark Brown 
--
v2:
	- Style correction
	- Can accept platform_data with invalid GPIOs
	- Removed unnecessary features
	- Improved error handling
Signed-off-by: Liam Girdwood