From 8202bc29454cfdd5839058e4b79c36a3fbb221cf Mon Sep 17 00:00:00 2001 From: Eugen Hristev <eugen.hristev@collabora.com> Date: Wed, 19 Apr 2023 16:45:26 +0300 Subject: [PATCH] regulator: handle different error codes in regulator_set_enable_if_allowed The regulator core can return different codes which are not considered a real error for this function. Return success in such cases. Signed-off-by: Eugen Hristev <eugen.hristev@collabora.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Patrice Chotard <patrice.chotard@foss.st.com> --- drivers/power/regulator/regulator-uclass.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/drivers/power/regulator/regulator-uclass.c b/drivers/power/regulator/regulator-uclass.c index d608f7c236..3a6ba69f6d 100644 --- a/drivers/power/regulator/regulator-uclass.c +++ b/drivers/power/regulator/regulator-uclass.c @@ -197,6 +197,12 @@ int regulator_set_enable_if_allowed(struct udevice *dev, bool enable) ret = regulator_set_enable(dev, enable); if (ret == -ENOSYS || ret == -EACCES) return 0; + /* if we want to disable but it's in use by someone else */ + if (!enable && ret == -EBUSY) + return 0; + /* if it's already enabled/disabled */ + if (ret == -EALREADY) + return 0; return ret; } -- 2.39.5