For now, regulator registers only looks for parent supplies in the struct device of_node.
That means that single devices that expose several regulators in the DT have to tie the parent supplies to the parent device, instead of the regulator itself like described in the regulator bindings. The regulator device node is already present in the regulator_config structure that is passed to regulator_register. Use it to first match in the regulator node, and then to the device node itself. Signed-off-by: Maxime Ripard <[email protected]> --- drivers/regulator/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index 3e3954252a23..c8e26be5ea01 100644 --- a/drivers/regulator/core.c +++ b/drivers/regulator/core.c @@ -3503,7 +3503,7 @@ regulator_register(const struct regulator_desc *regulator_desc, if (supply) { struct regulator_dev *r; - r = regulator_dev_lookup(dev, NULL, supply, &ret); + r = regulator_dev_lookup(dev, config->of_node, supply, &ret); if (ret == -ENODEV) { /* -- 1.9.3 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
