linux-toradex.git/drivers/regulator/of_regulator.c, branch v4.0-rc1

regulator: Allow parsing custom properties when using simplified DT parsing

2015-01-08T20:15:45+00:00

When drivers use simplified DT parsing method (they provide
'regulator_desc.of_match') they still may want to parse custom
properties for some of the regulators. For example some of the
regulators support GPIO enable control.

Add a driver-supplied callback for such case. This way the regulator
core parses common bindings offloading a lot of code from drivers and
still custom properties may be used.

The callback, called for each parsed regulator, may modify the
'regulator_config' initially passed to regulator_register().

Signed-off-by: Krzysztof Kozlowski 
Signed-off-by: Mark Brown

Merge tag 'v3.18-rc4' into regulator-max77802

2014-11-26T20:37:57+00:00

Linux 3.18-rc4

regulator: of: Add support for parsing initial and suspend modes

2014-11-26T18:58:14+00:00

Some regulators support their operating mode to be changed on startup
or by consumers when the system is running while others only support
their operating mode to be changed while the system has entered in a
suspend state.

The regulator Device Tree binding documents a set of properties to
configure the regulators operating modes from a FDT. This patch builds
on (40e20d6 regulator: of: Add support for parsing regulator_state for
suspend state) and adds support to parse those properties and fill the
regulator constraints so the regulator core can call the right suspend
handlers when the system enters into sleep.

The modes are defined in the Device Tree using the hardware specific
modes supported by the regulators. Regulator drivers have to define a
translation function that is used to map the hardware specific modes
to the standard ones.

Signed-off-by: Javier Martinez Canillas 
Signed-off-by: Mark Brown

regulator: of: Pass the regulator description in the match table

2014-11-26T18:58:14+00:00

Drivers can use the of_regulator_match() function to parse the regulator
init_data from DT. A match table is used to specify the name of the node
containing the regulators, the device node and to return the init_data
to the caller.

But also the static regulator descriptor is needed to correctly extract
some DT properties like the regulator initial and suspend modes. Use the
match table to pass that information.

Signed-off-by: Javier Martinez Canillas 
Signed-off-by: Mark Brown

regulator: of: Add regulator desc param to of_get_regulator_init_data()

2014-11-26T18:58:14+00:00

The of_get_regulator_init_data() function is used to extract the regulator
init_data but information on how to extract certain data is defined in the
static regulator descriptor (e.g: how to map the hardware operating modes).

Add a const struct regulator_desc * parameter to the function signature so
the parsing logic could use the information in the struct regulator_desc.

of_get_regulator_init_data() relies on of_get_regulation_constraints() to
actually extract the init_data so it has to pass the struct regulator_desc
but that is modified on a later patch.

Signed-off-by: Javier Martinez Canillas 
Signed-off-by: Mark Brown

regulator: of: Add support for parsing microvolts for suspend state

2014-11-03T12:29:02+00:00

Leverage all the work that was done in (40e20d6 regulator: of: Add
support for parsing regulator_state for suspend state) and throw in
the ability to set suspend microvolts from the device tree.

Signed-off-by: Doug Anderson 
Reviewed-by: Javier Martinez Canillas 
Reviewed-by: Chris Zhong 
Signed-off-by: Mark Brown

regulator: Staticize 'regulator_states' array

2014-10-31T18:13:38+00:00

The 'regulator_states' array is used only in this unit and it is not
exported. Make it static.

This also fixes following sparse warning:
drivers/regulator/of_regulator.c:22:12: warning: symbol 'regulator_states' was not declared. Should it be static?

Signed-off-by: Krzysztof Kozlowski 
Signed-off-by: Mark Brown

regulator: of: Lower the severity of the error with no container

2014-10-29T12:36:21+00:00

Description of regulators should generally be optional so if there is no
DT node for the regulators container then we shouldn't print an error
message. Lower the severity of the message to debug level (it might help
someone work out what went wrong) and while we're at it say what we were
looking for.

Reported-by: Guenter Roeck 
Signed-off-by: Mark Brown

regulator: of: Decrement refcount for suspend state nodes

2014-10-22T16:34:36+00:00

of_get_regulation_constraints() calls of_get_child_by_name() to find the
regulator-state-{mem,disk} child nodes for each regulator. This function
increments the device node reference counter but this is not decremented
once the function is done using the node.

Fix that by calling of_node_put() after finishing using the device node.

Signed-off-by: Javier Martinez Canillas 
Signed-off-by: Mark Brown

regulator: of: Add support for parsing regulator_state for suspend state

2014-10-20T11:24:13+00:00

The regulation_constraints structure includes specific field to support
suspend state for global PMIC SUSPEND/HIBERNATE mode. This patch add support
for parsing regulator_state for suspend state.

Signed-off-by: Chanwoo Choi 
Acked-by: Kyungmin Park 
Signed-off-by: Mark Brown