Commit 96e20adc authored by Matti Vaittinen's avatar Matti Vaittinen Committed by Mark Brown

regulator: change stubbed devm_regulator_get_enable to return Ok

The devm_regulator_get_enable() should be a 'call and forget' API,
meaning, when it is used to enable the regulators, the API does not
provide a handle to do any further control of the regulators. It gives
no real benefit to return an error from the stub if CONFIG_REGULATOR is
not set.

On the contrary, returning and error is causing problems to drivers when
hardware is such it works out just fine with no regulator control.
Returning an error forces drivers to specifically handle the case where
CONFIG_REGULATOR is not set, making the mere existence of the stub
questionalble. Furthermore, the stub of the regulator_enable() seems to
be returning Ok.

Change the stub implementation for the devm_regulator_get_enable() to
return Ok so drivers do not separately handle the case where the
CONFIG_REGULATOR is not set.
Signed-off-by: default avatarMatti Vaittinen <mazziesaccount@gmail.com>
Reported-by: default avatarAleksander Mazur <deweloper@wp.pl>
Suggested-by: default avatarGuenter Roeck <linux@roeck-us.net>
Fixes: da279e69 ("regulator: Add devm helpers for get and enable")
Reviewed-by: default avatarGuenter Roeck <linux@roeck-us.net>
Link: https://lore.kernel.org/r/ZiYF6d1V1vSPcsJS@drtxq0yyyyyyyyyyyyyby-3.rev.dnainternet.fiSigned-off-by: default avatarMark Brown <broonie@kernel.org>
parent 68adb581
...@@ -320,7 +320,7 @@ devm_regulator_get_exclusive(struct device *dev, const char *id) ...@@ -320,7 +320,7 @@ devm_regulator_get_exclusive(struct device *dev, const char *id)
static inline int devm_regulator_get_enable(struct device *dev, const char *id) static inline int devm_regulator_get_enable(struct device *dev, const char *id)
{ {
return -ENODEV; return 0;
} }
static inline int devm_regulator_get_enable_optional(struct device *dev, static inline int devm_regulator_get_enable_optional(struct device *dev,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment