diff options
| author | Axel Lin <axel.lin@ingics.com> | 2014-02-22 12:53:18 +0800 |
|---|---|---|
| committer | Nitin Garg <nitin.garg@freescale.com> | 2015-09-17 08:57:39 -0500 |
| commit | 1f1def239369bcd902a16a8ccbec285ec4aa0071 (patch) | |
| tree | a92bd51fb29b25af918f786ceadb8b41b3014c54 /drivers/regulator/dbx500-prcmu.h | |
| parent | 97bc0a08da5d8ff81d64e0be448c335673e1c93d (diff) | |
regulator: anatop: Remove checking control_reg in [set|get]_voltage_sel
Remove checking control_reg in [set|get]_voltage_sel and then convert to use
regulator_[set|get]_voltage_sel_regmap for [set|get]_voltage_sel callbacks.
The anatop-reg-offset property is a required property rather than optional
property. So the question is what is the meaning of setting anatop-reg-offset
to 0? If 0 is a valid setting for anatop-reg-offset and it has special meaning,
we had better document it in the binding document. Otherwise, remove the testing
for control_reg in the driver.
No anatop voltage regulator node in the dts files set anatop-reg-offset to 0.
So I think it's safe to remove testing if control_reg is 0.
Signed-off-by: Axel Lin <axel.lin@ingics.com>
Signed-off-by: Mark Brown <broonie@linaro.org>
[shawn.guo: cherry-pick commit 114c5748d540 from upstream]
Signed-off-by: Shawn Guo <shawn.guo@freescale.com>
Diffstat (limited to 'drivers/regulator/dbx500-prcmu.h')
0 files changed, 0 insertions, 0 deletions