power: regulator: Add limits checking while setting current
authorKeerthy <j-keerthy@ti.com>
Wed, 26 Oct 2016 08:12:32 +0000 (13:42 +0530)
committerSimon Glass <sjg@chromium.org>
Sat, 26 Nov 2016 00:59:26 +0000 (17:59 -0700)
Currently the specific set ops functions are directly
called without any check for min/max current limits for a regulator.
Check for them and proceed.

Signed-off-by: Keerthy <j-keerthy@ti.com>
Fixed checking of current limits:
Signed-off-by: Simon Glass <sjg@chromium.org>
drivers/power/regulator/regulator-uclass.c

index e48d2132889cfabf02b25f06d2227db5171f12bb..52a107036325e2fb31d150e7fd3890d3f72432df 100644 (file)
@@ -82,6 +82,13 @@ int regulator_get_current(struct udevice *dev)
 int regulator_set_current(struct udevice *dev, int uA)
 {
        const struct dm_regulator_ops *ops = dev_get_driver_ops(dev);
+       struct dm_regulator_uclass_platdata *uc_pdata;
+
+       uc_pdata = dev_get_uclass_platdata(dev);
+       if (uc_pdata->min_uA != -ENODATA && uA < uc_pdata->min_uA)
+               return -EINVAL;
+       if (uc_pdata->max_uA != -ENODATA && uA > uc_pdata->max_uA)
+               return -EINVAL;
 
        if (!ops || !ops->set_current)
                return -ENOSYS;