diff options
author | Philipp Zabel <p.zabel@pengutronix.de> | 2018-08-31 15:34:02 +0300 |
---|---|---|
committer | Mark Brown <broonie@kernel.org> | 2018-08-31 17:55:54 +0300 |
commit | ef394f3fbecbe61d69450ad8cf0fa8f713c8ce8f (patch) | |
tree | 8555fac064ba3f18fa9e58571f45cacac890acd1 /drivers/regulator/of_regulator.c | |
parent | 823f18f8b860526fc099c222619a126d57d2ad8c (diff) | |
download | linux-ef394f3fbecbe61d69450ad8cf0fa8f713c8ce8f.tar.xz |
regulator: da9063: fix DT probing with constraints
Commit 1c892e38ce59 ("regulator: da9063: Handle less LDOs on DA9063L")
reordered the da9063_regulator_info[] array, but not the DA9063_ID_*
regulator ids and not the da9063_matches[] array, because ids are used
as indices in the array initializer. This mismatch between regulator id
and da9063_regulator_info[] array index causes the driver probe to fail
because constraints from DT are not applied to the correct regulator:
da9063 0-0058: Device detected (chip-ID: 0x61, var-ID: 0x50)
DA9063_BMEM: Bringing 900000uV into 3300000-3300000uV
DA9063_LDO9: Bringing 3300000uV into 2500000-2500000uV
DA9063_LDO1: Bringing 900000uV into 3300000-3300000uV
DA9063_LDO1: failed to apply 3300000-3300000uV constraint(-22)
This patch reorders the DA9063_ID_* as apparently intended, and with
them the entries in the da90630_matches[] array.
Fixes: 1c892e38ce59 ("regulator: da9063: Handle less LDOs on DA9063L")
Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Marek Vasut <marek.vasut@gmail.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers/regulator/of_regulator.c')
0 files changed, 0 insertions, 0 deletions