2011-11-18 11:17:17 +00:00
|
|
|
/*
|
|
|
|
* OF helpers for regulator framework
|
|
|
|
*
|
|
|
|
* Copyright (C) 2011 Texas Instruments, Inc.
|
|
|
|
* Rajendra Nayak <rnayak@ti.com>
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
* the Free Software Foundation; either version 2 of the License, or
|
|
|
|
* (at your option) any later version.
|
|
|
|
*/
|
|
|
|
|
2011-11-26 10:50:58 +00:00
|
|
|
#include <linux/module.h>
|
2011-11-18 11:17:17 +00:00
|
|
|
#include <linux/slab.h>
|
|
|
|
#include <linux/of.h>
|
|
|
|
#include <linux/regulator/machine.h>
|
2012-04-26 14:52:20 +00:00
|
|
|
#include <linux/regulator/of_regulator.h>
|
2011-11-18 11:17:17 +00:00
|
|
|
|
|
|
|
static void of_get_regulation_constraints(struct device_node *np,
|
|
|
|
struct regulator_init_data **init_data)
|
|
|
|
{
|
2014-05-26 20:27:19 +00:00
|
|
|
const __be32 *min_uV, *max_uV;
|
2011-11-18 11:17:17 +00:00
|
|
|
struct regulation_constraints *constraints = &(*init_data)->constraints;
|
2013-09-18 12:48:02 +00:00
|
|
|
int ret;
|
|
|
|
u32 pval;
|
2011-11-18 11:17:17 +00:00
|
|
|
|
|
|
|
constraints->name = of_get_property(np, "regulator-name", NULL);
|
|
|
|
|
|
|
|
min_uV = of_get_property(np, "regulator-min-microvolt", NULL);
|
|
|
|
if (min_uV)
|
|
|
|
constraints->min_uV = be32_to_cpu(*min_uV);
|
|
|
|
max_uV = of_get_property(np, "regulator-max-microvolt", NULL);
|
|
|
|
if (max_uV)
|
|
|
|
constraints->max_uV = be32_to_cpu(*max_uV);
|
|
|
|
|
|
|
|
/* Voltage change possible? */
|
|
|
|
if (constraints->min_uV != constraints->max_uV)
|
|
|
|
constraints->valid_ops_mask |= REGULATOR_CHANGE_VOLTAGE;
|
2011-12-05 10:58:41 +00:00
|
|
|
/* Only one voltage? Then make sure it's set. */
|
2012-01-25 09:31:45 +00:00
|
|
|
if (min_uV && max_uV && constraints->min_uV == constraints->max_uV)
|
2011-12-05 10:58:41 +00:00
|
|
|
constraints->apply_uV = true;
|
2011-11-18 11:17:17 +00:00
|
|
|
|
2014-05-26 20:27:19 +00:00
|
|
|
if (!of_property_read_u32(np, "regulator-microvolt-offset", &pval))
|
|
|
|
constraints->uV_offset = pval;
|
|
|
|
if (!of_property_read_u32(np, "regulator-min-microamp", &pval))
|
|
|
|
constraints->min_uA = pval;
|
|
|
|
if (!of_property_read_u32(np, "regulator-max-microamp", &pval))
|
|
|
|
constraints->max_uA = pval;
|
2011-11-18 11:17:17 +00:00
|
|
|
|
|
|
|
/* Current change possible? */
|
|
|
|
if (constraints->min_uA != constraints->max_uA)
|
|
|
|
constraints->valid_ops_mask |= REGULATOR_CHANGE_CURRENT;
|
|
|
|
|
2014-05-26 20:27:19 +00:00
|
|
|
constraints->boot_on = of_property_read_bool(np, "regulator-boot-on");
|
|
|
|
constraints->always_on = of_property_read_bool(np, "regulator-always-on");
|
|
|
|
if (!constraints->always_on) /* status change should be possible. */
|
2011-11-18 11:17:17 +00:00
|
|
|
constraints->valid_ops_mask |= REGULATOR_CHANGE_STATUS;
|
2012-06-11 12:11:08 +00:00
|
|
|
|
2013-06-20 08:37:37 +00:00
|
|
|
if (of_property_read_bool(np, "regulator-allow-bypass"))
|
|
|
|
constraints->valid_ops_mask |= REGULATOR_CHANGE_BYPASS;
|
|
|
|
|
2014-05-26 20:27:19 +00:00
|
|
|
ret = of_property_read_u32(np, "regulator-ramp-delay", &pval);
|
|
|
|
if (!ret) {
|
|
|
|
if (pval)
|
|
|
|
constraints->ramp_delay = pval;
|
2013-06-29 12:51:15 +00:00
|
|
|
else
|
|
|
|
constraints->ramp_disable = true;
|
|
|
|
}
|
2013-09-18 12:48:02 +00:00
|
|
|
|
|
|
|
ret = of_property_read_u32(np, "regulator-enable-ramp-delay", &pval);
|
|
|
|
if (!ret)
|
|
|
|
constraints->enable_time = pval;
|
2011-11-18 11:17:17 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* of_get_regulator_init_data - extract regulator_init_data structure info
|
|
|
|
* @dev: device requesting for regulator_init_data
|
|
|
|
*
|
|
|
|
* Populates regulator_init_data structure by extracting data from device
|
|
|
|
* tree node, returns a pointer to the populated struture or NULL if memory
|
|
|
|
* alloc fails.
|
|
|
|
*/
|
2011-12-01 09:21:06 +00:00
|
|
|
struct regulator_init_data *of_get_regulator_init_data(struct device *dev,
|
|
|
|
struct device_node *node)
|
2011-11-18 11:17:17 +00:00
|
|
|
{
|
|
|
|
struct regulator_init_data *init_data;
|
|
|
|
|
2011-12-01 09:21:06 +00:00
|
|
|
if (!node)
|
2011-11-18 11:17:17 +00:00
|
|
|
return NULL;
|
|
|
|
|
|
|
|
init_data = devm_kzalloc(dev, sizeof(*init_data), GFP_KERNEL);
|
|
|
|
if (!init_data)
|
|
|
|
return NULL; /* Out of memory? */
|
|
|
|
|
2011-12-01 09:21:06 +00:00
|
|
|
of_get_regulation_constraints(node, &init_data);
|
2011-11-18 11:17:17 +00:00
|
|
|
return init_data;
|
|
|
|
}
|
2011-11-26 10:50:58 +00:00
|
|
|
EXPORT_SYMBOL_GPL(of_get_regulator_init_data);
|
2012-04-26 14:52:20 +00:00
|
|
|
|
2014-04-15 12:34:36 +00:00
|
|
|
struct devm_of_regulator_matches {
|
|
|
|
struct of_regulator_match *matches;
|
|
|
|
unsigned int num_matches;
|
|
|
|
};
|
|
|
|
|
|
|
|
static void devm_of_regulator_put_matches(struct device *dev, void *res)
|
|
|
|
{
|
|
|
|
struct devm_of_regulator_matches *devm_matches = res;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < devm_matches->num_matches; i++)
|
|
|
|
of_node_put(devm_matches->matches[i].of_node);
|
|
|
|
}
|
|
|
|
|
2012-04-26 14:52:20 +00:00
|
|
|
/**
|
regulator: deprecate regulator-compatible DT property
When the bindings for the TPS6586x regulator were being proposed, I
asserted that DT node naming rules for bus child nodes should also be
applied to nodes inside the TPS6586x regulator node itself. In other
words, that each node providing regulator init data should be named
after the type of object it represented ("regulator") and hence that
some other property was required to indicate which regulator the node
described ("regulator-compatible"). In turn this led to multiple nodes
having the same name, thus requiring node names to use a unit address
to make them unique, thus requiring reg properties within the nodes and
However, subsequent discussion indicates that the rules I was asserting
only applies to standardized bus nodes, and within a device's own node,
the binding can basically do anything sane that it wants.
Hence, this change deprecates the register-compatible property, and
instead uses node names to replace this functionality. This greatly
simplifies the device tree content, making them smaller and more legible.
The code is changed such that old device trees continue to work.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
2012-09-24 19:25:00 +00:00
|
|
|
* of_regulator_match - extract multiple regulator init data from device tree.
|
2012-04-26 14:52:20 +00:00
|
|
|
* @dev: device requesting the data
|
|
|
|
* @node: parent device node of the regulators
|
|
|
|
* @matches: match table for the regulators
|
|
|
|
* @num_matches: number of entries in match table
|
|
|
|
*
|
regulator: deprecate regulator-compatible DT property
When the bindings for the TPS6586x regulator were being proposed, I
asserted that DT node naming rules for bus child nodes should also be
applied to nodes inside the TPS6586x regulator node itself. In other
words, that each node providing regulator init data should be named
after the type of object it represented ("regulator") and hence that
some other property was required to indicate which regulator the node
described ("regulator-compatible"). In turn this led to multiple nodes
having the same name, thus requiring node names to use a unit address
to make them unique, thus requiring reg properties within the nodes and
However, subsequent discussion indicates that the rules I was asserting
only applies to standardized bus nodes, and within a device's own node,
the binding can basically do anything sane that it wants.
Hence, this change deprecates the register-compatible property, and
instead uses node names to replace this functionality. This greatly
simplifies the device tree content, making them smaller and more legible.
The code is changed such that old device trees continue to work.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
2012-09-24 19:25:00 +00:00
|
|
|
* This function uses a match table specified by the regulator driver to
|
|
|
|
* parse regulator init data from the device tree. @node is expected to
|
|
|
|
* contain a set of child nodes, each providing the init data for one
|
|
|
|
* regulator. The data parsed from a child node will be matched to a regulator
|
|
|
|
* based on either the deprecated property regulator-compatible if present,
|
|
|
|
* or otherwise the child node's name. Note that the match table is modified
|
2014-04-03 14:32:15 +00:00
|
|
|
* in place and an additional of_node reference is taken for each matched
|
|
|
|
* regulator.
|
2012-04-26 14:52:20 +00:00
|
|
|
*
|
|
|
|
* Returns the number of matches found or a negative error code on failure.
|
|
|
|
*/
|
|
|
|
int of_regulator_match(struct device *dev, struct device_node *node,
|
|
|
|
struct of_regulator_match *matches,
|
|
|
|
unsigned int num_matches)
|
|
|
|
{
|
|
|
|
unsigned int count = 0;
|
|
|
|
unsigned int i;
|
regulator: deprecate regulator-compatible DT property
When the bindings for the TPS6586x regulator were being proposed, I
asserted that DT node naming rules for bus child nodes should also be
applied to nodes inside the TPS6586x regulator node itself. In other
words, that each node providing regulator init data should be named
after the type of object it represented ("regulator") and hence that
some other property was required to indicate which regulator the node
described ("regulator-compatible"). In turn this led to multiple nodes
having the same name, thus requiring node names to use a unit address
to make them unique, thus requiring reg properties within the nodes and
However, subsequent discussion indicates that the rules I was asserting
only applies to standardized bus nodes, and within a device's own node,
the binding can basically do anything sane that it wants.
Hence, this change deprecates the register-compatible property, and
instead uses node names to replace this functionality. This greatly
simplifies the device tree content, making them smaller and more legible.
The code is changed such that old device trees continue to work.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
2012-09-24 19:25:00 +00:00
|
|
|
const char *name;
|
2012-06-20 12:23:06 +00:00
|
|
|
struct device_node *child;
|
2014-04-15 12:34:36 +00:00
|
|
|
struct devm_of_regulator_matches *devm_matches;
|
2012-04-26 14:52:20 +00:00
|
|
|
|
|
|
|
if (!dev || !node)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2014-04-15 12:34:36 +00:00
|
|
|
devm_matches = devres_alloc(devm_of_regulator_put_matches,
|
|
|
|
sizeof(struct devm_of_regulator_matches),
|
|
|
|
GFP_KERNEL);
|
|
|
|
if (!devm_matches)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
devm_matches->matches = matches;
|
|
|
|
devm_matches->num_matches = num_matches;
|
|
|
|
|
|
|
|
devres_add(dev, devm_matches);
|
|
|
|
|
2013-01-29 19:01:13 +00:00
|
|
|
for (i = 0; i < num_matches; i++) {
|
|
|
|
struct of_regulator_match *match = &matches[i];
|
|
|
|
match->init_data = NULL;
|
|
|
|
match->of_node = NULL;
|
|
|
|
}
|
|
|
|
|
2012-06-20 12:23:06 +00:00
|
|
|
for_each_child_of_node(node, child) {
|
regulator: deprecate regulator-compatible DT property
When the bindings for the TPS6586x regulator were being proposed, I
asserted that DT node naming rules for bus child nodes should also be
applied to nodes inside the TPS6586x regulator node itself. In other
words, that each node providing regulator init data should be named
after the type of object it represented ("regulator") and hence that
some other property was required to indicate which regulator the node
described ("regulator-compatible"). In turn this led to multiple nodes
having the same name, thus requiring node names to use a unit address
to make them unique, thus requiring reg properties within the nodes and
However, subsequent discussion indicates that the rules I was asserting
only applies to standardized bus nodes, and within a device's own node,
the binding can basically do anything sane that it wants.
Hence, this change deprecates the register-compatible property, and
instead uses node names to replace this functionality. This greatly
simplifies the device tree content, making them smaller and more legible.
The code is changed such that old device trees continue to work.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
2012-09-24 19:25:00 +00:00
|
|
|
name = of_get_property(child,
|
2012-06-20 12:23:06 +00:00
|
|
|
"regulator-compatible", NULL);
|
regulator: deprecate regulator-compatible DT property
When the bindings for the TPS6586x regulator were being proposed, I
asserted that DT node naming rules for bus child nodes should also be
applied to nodes inside the TPS6586x regulator node itself. In other
words, that each node providing regulator init data should be named
after the type of object it represented ("regulator") and hence that
some other property was required to indicate which regulator the node
described ("regulator-compatible"). In turn this led to multiple nodes
having the same name, thus requiring node names to use a unit address
to make them unique, thus requiring reg properties within the nodes and
However, subsequent discussion indicates that the rules I was asserting
only applies to standardized bus nodes, and within a device's own node,
the binding can basically do anything sane that it wants.
Hence, this change deprecates the register-compatible property, and
instead uses node names to replace this functionality. This greatly
simplifies the device tree content, making them smaller and more legible.
The code is changed such that old device trees continue to work.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
2012-09-24 19:25:00 +00:00
|
|
|
if (!name)
|
|
|
|
name = child->name;
|
2012-06-20 12:23:06 +00:00
|
|
|
for (i = 0; i < num_matches; i++) {
|
|
|
|
struct of_regulator_match *match = &matches[i];
|
|
|
|
if (match->of_node)
|
|
|
|
continue;
|
|
|
|
|
regulator: deprecate regulator-compatible DT property
When the bindings for the TPS6586x regulator were being proposed, I
asserted that DT node naming rules for bus child nodes should also be
applied to nodes inside the TPS6586x regulator node itself. In other
words, that each node providing regulator init data should be named
after the type of object it represented ("regulator") and hence that
some other property was required to indicate which regulator the node
described ("regulator-compatible"). In turn this led to multiple nodes
having the same name, thus requiring node names to use a unit address
to make them unique, thus requiring reg properties within the nodes and
However, subsequent discussion indicates that the rules I was asserting
only applies to standardized bus nodes, and within a device's own node,
the binding can basically do anything sane that it wants.
Hence, this change deprecates the register-compatible property, and
instead uses node names to replace this functionality. This greatly
simplifies the device tree content, making them smaller and more legible.
The code is changed such that old device trees continue to work.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
2012-09-24 19:25:00 +00:00
|
|
|
if (strcmp(match->name, name))
|
2012-06-20 12:23:06 +00:00
|
|
|
continue;
|
|
|
|
|
|
|
|
match->init_data =
|
|
|
|
of_get_regulator_init_data(dev, child);
|
|
|
|
if (!match->init_data) {
|
|
|
|
dev_err(dev,
|
|
|
|
"failed to parse DT for regulator %s\n",
|
|
|
|
child->name);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
2014-04-03 14:32:15 +00:00
|
|
|
match->of_node = of_node_get(child);
|
2012-06-20 12:23:06 +00:00
|
|
|
count++;
|
|
|
|
break;
|
2012-04-26 14:52:20 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return count;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(of_regulator_match);
|