diff options
author | Charles Keepax <ckeepax@opensource.wolfsonmicro.com> | 2017-06-13 16:12:47 +0100 |
---|---|---|
committer | Mark Brown <broonie@kernel.org> | 2017-06-13 18:43:28 +0100 |
commit | 062171973e05440673cb997e64395e84a8e66350 (patch) | |
tree | 062848ea7b019f630704ae5fcb5ddb0fabae624a /Kconfig | |
parent | 2ea659a9ef488125eb46da6eb571de5eae5c43f6 (diff) | |
download | linux-062171973e05440673cb997e64395e84a8e66350.tar.bz2 |
regulator: core: Prioritise consumer mappings over regulator name
Currently, when looking up a regulator supply, the regulator name
takes priority over the consumer mappings. As there are a lot of
regulator names that are in fairly common use (VDD, MICVDD, etc.) this
can easily lead to obtaining the wrong supply, when a system contains
two regulators that share a name.
The explicit consumer mappings contain much less ambiguity as they
specify both a name and a consumer device. As such prioritise those if
one exists and only fall back to the regulator name if there are no
matching explicit mappings.
Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions