regulator: da9063: Fix notifier mutex lock warning
authorSteve Twiss <stwiss.opensource@diasemi.com>
Tue, 26 Feb 2019 15:23:02 +0000 (15:23 +0000)
committerMark Brown <broonie@kernel.org>
Wed, 13 Mar 2019 15:11:11 +0000 (15:11 +0000)
The mutex for the regulator_dev must be controlled by the caller of
the regulator_notifier_call_chain(), as described in the comment
for that function.

Failure to mutex lock and unlock surrounding the notifier call results
in a kernel WARN_ON_ONCE() which will dump a backtrace for the
regulator_notifier_call_chain() when that function call is first made.
The mutex can be controlled using the regulator_lock/unlock() API.

Fixes: 69ca3e58d178 ("regulator: da9063: Add Dialog DA9063 voltage regulators support.")
Suggested-by: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
drivers/regulator/da9063-regulator.c

index 2b0c7a85306abe81688a973d775a546dae7dbf56..d7bdb95b7602e68e4d31ac8856c3b83cf38559ab 100644 (file)
@@ -615,9 +615,12 @@ static irqreturn_t da9063_ldo_lim_event(int irq, void *data)
                if (regl->info->oc_event.reg != DA9063_REG_STATUS_D)
                        continue;
 
-               if (BIT(regl->info->oc_event.lsb) & bits)
+               if (BIT(regl->info->oc_event.lsb) & bits) {
+                       regulator_lock(regl->rdev);
                        regulator_notifier_call_chain(regl->rdev,
                                        REGULATOR_EVENT_OVER_CURRENT, NULL);
+                       regulator_unlock(regl->rdev);
+               }
        }
 
        return IRQ_HANDLED;