linux-toradex.git/include/linux/regulator/driver.h, branch v2.6.36-rc8

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

regulator: Add regulator_get_exclusive() API

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

Some consumers require complete control of the regulator and can't
tolerate sharing it with other consumers, most commonly because they need
to have the regulator actually disabled so can't have other consumers
forcing it on. This new regulator_get_exclusive() API call allows these
consumers to explicitly request this, documenting the assumptions that
they are making.

In order to simplify coding of such consumers the use count for regulators
they request is forced to match the enabled state of the regulator when
it is requested. This is not possible for consumers which can share
regulators due to the need to keep track of the ownership of use counts.

A new API call is used rather than an additional argument to the existing
regulator_get() in order to avoid merge headaches with driver code in
other trees.

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

regulator: Provide mode to status conversion function

2009-09-17T07:47:05+00:00

This is useful for implementing get_status() in terms of get_mode().

Signed-off-by: Mark Brown 
Signed-off-by: Samuel Ortiz

regulator: fix header file missing kernel-doc

2009-04-28T17:58:06+00:00

Add regulator header file missing kernel-doc:

Warning(include/linux/regulator/driver.h:117): No description found for parameter 'set_mode'

Signed-off-by: Randy Dunlap 
cc:	Liam Girdwood 
cc:	Mark Brown 
Signed-off-by: Liam Girdwood

regulator: get_status() grows kerneldoc

2009-03-31T08:56:25+00:00

Add kerneldoc for the new get_status() message.  Fix the existing
kerneldoc for that struct in two ways:

 (a) Syntax, making sure parameter descriptions immediately
     follow the one-line struct description and that the first
     blank lines is before any more expansive description;
 (b) Presentation for a few points, to highlight the fact that
     the previous "get" methods exist only to report the current
     configuration, not to display actual status.

Signed-off-by: David Brownell 
Signed-off-by: Liam Girdwood

regulator: enumerate voltages (v2)

2009-03-31T08:56:24+00:00

Add a basic mechanism for regulators to report the discrete
voltages they support:  list_voltage() enumerates them using
selectors numbered from 0 to an upper bound.

Use those methods to force machine-level constraints into bounds.
(Example:  regulator supports 1.8V, 2.4V, 2.6V, 3.3V, and board
constraints for that rail are 2.0V to 3.6V ... so the range of
voltages is then 2.4V to 3.3V on this board.)

Export those voltages to the regulator consumer interface, so for
example regulator hooked up to an MMC/SD/SDIO slot can report the
actual voltage options available to cards connected there.

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

regulator: email - update email address and regulator webpage.

2009-03-31T08:56:23+00:00

Remove deceased email address and update to new address. Also update
website details in MAINTAINERS with correct page.

Signed-off-by: Liam Girdwood

regulator: fix header file missing kernel-doc

2009-03-31T08:56:22+00:00

Fix regulator/driver.h missing kernel-doc:

Warning(linux-next-20090120//include/linux/regulator/driver.h:108): No description found for parameter 'get_status'

Signed-off-by: Randy Dunlap 
cc: Liam Girdwood 
cc: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: Hoist struct regulator_dev out of core to fix notifiers

2009-03-31T08:56:22+00:00

Commit 872ed3fe176833f7d43748eb88010da4bbd2f983 caused regulator drivers
to take the struct regulator_dev lock themselves which requires that the
struct be visible to them. Band aid this by making the struct visible.

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