From: "Nuno Sá" <noname.nuno@gmail.com>
To: "Andrey Skvortsov" <andrej.skvortzov@gmail.com>,
"Jean-Baptiste Maneyrol" <jean-baptiste.maneyrol@tdk.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Jonathan Marek" <jonathan@marek.ca>,
"Brian Masney" <masneyb@onstation.org>,
"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH v2 3/3] iio: imu: inv_mpu6050: fix unbalanced regulator_disable calls, when probe fails
Date: Sat, 11 Apr 2026 14:22:04 +0100 [thread overview]
Message-ID: <deaaa498f1036ef39e66cca3d00b54148f4d7547.camel@gmail.com> (raw)
In-Reply-To: <20260401082737.781018-4-andrej.skvortzov@gmail.com>
On Wed, 2026-04-01 at 11:27 +0300, Andrey Skvortsov wrote:
> During a probe functions after all regulators are enabled, runtime pm
> is enabled. Before probe function finishes, runtime pm triggers and
> disables vddio regulator. When probe function fails after that,
> inv_mpu_core_disable_regulator_action tries to disable already
> disabled by runtime pm vddio regulator causing following backtrace:
>
> inv-mpu6050-i2c 1-0068: trigger probe fail -19
> WARNING: drivers/regulator/core.c:3244 at _regulator_disable+0x2ac/0x600
> Call trace:
> _regulator_disable+0x2ac/0x600 (P)
> regulator_disable+0xac/0x148
> inv_mpu_core_disable_regulator_vddio_action+0x3c/0xb0 [inv_mpu6050]
> devm_action_release+0x4c/0x88
> release_nodes+0xd8/0x178
> devres_release_group+0x214/0x3c8
> i2c_device_probe+0x6fc/0x9b0
> ...
> inv-mpu6050-i2c 1-0068: Failed to disable vddio regulator: -5
>
> Fix the issue by checking runtime suspend status, when vddio regulator
> is disabled. To handle this correctly pm_runtime active status has to
> be set early before vddio regulator setup.
The above looks a bit hacky. We're playing with runtime status for things to work.
Also, setting the active state makes sense logically when the device is up and
running.
Maybe we should just move enabling runtime to the end of the probe function?
Also, fixes should come first in the series in case we want to backport them.
- Nuno Sá
>
> Signed-off-by: Andrey Skvortsov <andrej.skvortzov@gmail.com>
> Fixes: 07c12b1c007c ("iio: imu: mpu6050: add support for regulator framework")
> ---
> drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> b/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> index 3a57a3f440526..86e4d42c4d3d1 100644
> --- a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> +++ b/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> @@ -1862,8 +1862,10 @@ static int inv_mpu_core_disable_regulator_vddio(struct
> inv_mpu6050_state *st)
> static void inv_mpu_core_disable_regulator_vddio_action(void *_data)
> {
> struct inv_mpu6050_state *st = _data;
> + struct device *dev = regmap_get_device(st->map);
>
> - inv_mpu_core_disable_regulator_vddio(st);
> + if (!pm_runtime_status_suspended(dev))
> + inv_mpu_core_disable_regulator_vddio(st);
> }
>
>
> @@ -1953,6 +1955,11 @@ int inv_mpu_core_probe(struct regmap *regmap, int irq, const
> char *name,
>
> msleep(INV_MPU6050_POWER_UP_TIME);
>
> + /* set pm_runtime active early for disable vddio resource cleanup */
> + result = pm_runtime_set_active(dev);
> + if (result)
> + return result;
> +
> result = inv_mpu_core_enable_regulator_vddio(st);
> if (result)
> return result;
> @@ -1996,9 +2003,6 @@ int inv_mpu_core_probe(struct regmap *regmap, int irq, const
> char *name,
> }
>
> /* chip init is done, turning on runtime power management */
> - result = pm_runtime_set_active(dev);
> - if (result)
> - goto error_power_off;
> pm_runtime_get_noresume(dev);
> result = devm_pm_runtime_enable(dev);
> if (result)
next prev parent reply other threads:[~2026-04-11 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 8:27 [PATCH v2 0/3] iio: imu: inv_mpu6050: runtime pm fixes Andrey Skvortsov
2026-04-01 8:27 ` [PATCH v2 1/3] iio: imu: inv_mpu6050: use devres-enabled version of pm_runtime_enable Andrey Skvortsov
2026-04-01 15:00 ` Andy Shevchenko
2026-04-10 23:12 ` David Lechner
2026-04-01 8:27 ` [PATCH v2 2/3] iio: imu: inv_mpu6050: control vdd supply using devm-helpers Andrey Skvortsov
2026-04-01 15:10 ` Andy Shevchenko
2026-04-06 6:53 ` Andrey Skvortsov
2026-04-06 19:16 ` Andy Shevchenko
2026-04-01 8:27 ` [PATCH v2 3/3] iio: imu: inv_mpu6050: fix unbalanced regulator_disable calls, when probe fails Andrey Skvortsov
2026-04-11 13:22 ` Nuno Sá [this message]
2026-04-16 22:21 ` Andrey Skvortsov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=deaaa498f1036ef39e66cca3d00b54148f4d7547.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=andrej.skvortzov@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=jic23@kernel.org \
--cc=jonathan@marek.ca \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masneyb@onstation.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox