summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/regulator
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2016-06-09 10:49:02 +0100
committerMark Brown <broonie@kernel.org>2016-06-09 11:40:34 +0100
commitfc1e1c4a249e8bf0aff68576fad776dd5adc0562 (patch)
tree949d4b9136b85ee4e8c941f663ac7f4520996fc3 /Documentation/devicetree/bindings/regulator
parent1a695a905c18548062509178b98bc91e67510864 (diff)
downloadop-kernel-dev-fc1e1c4a249e8bf0aff68576fad776dd5adc0562.zip
op-kernel-dev-fc1e1c4a249e8bf0aff68576fad776dd5adc0562.tar.gz
regulator: Remove regulator_can_change_voltage()
There is little obvious use case for a regualtor driver to know if it is possible to vary voltages at all by itself. If a consumer needs to limit what voltages it tries to set based on the system configuration then it will need to enumerate the possible voltages, and without that even if it is possible to change voltages that doesn't mean that constraints or other consumers will allow whatever change the driver is trying to do at a given time. It doesn't even indicate if _set_voltage() calls will work as noop _set_voltage() calls return success. There were no users of this API that weren't abusing it and now they're all gone so remove the API. Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'Documentation/devicetree/bindings/regulator')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud