regulator: core: Log forbidden DRMS operation

When REGULATOR_CHANGE_DRMS is not set, drms_uA_update is a no-op.
It used to print a debug message, which was dropped in commit
8a34e979f684 ("regulator: refactor valid_ops_mask checking code")

Let's bring the debug message back, because it helps find missing
regulator-allow-set-load properties.

Signed-off-by: Marc Gonzalez <marc.w.gonzalez@free.fr>
Signed-off-by: Mark Brown <broonie@kernel.org>

diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 9cf09666616ff674560d352d726e605fbc6356e4..68473d0cc57e94f2b2af51d66ec3f3d448238af9 100644 (file)
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -918,8 +918,10 @@ static int drms_uA_update(struct regulator_dev *rdev)
         * first check to see if we can set modes at all, otherwise just
         * tell the consumer everything is OK.
         */
-       if (!regulator_ops_is_valid(rdev, REGULATOR_CHANGE_DRMS))
+       if (!regulator_ops_is_valid(rdev, REGULATOR_CHANGE_DRMS)) {
+               rdev_dbg(rdev, "DRMS operation not allowed\n");
                return 0;
+       }
 
        if (!rdev->desc->ops->get_optimum_mode &&
            !rdev->desc->ops->set_load)