From: Jonathan Cameron <jic23@kernel.org>
To: Sean Nyekjaer <sean@geanix.com>
Cc: "Jean-Baptiste Maneyrol" <jean-baptiste.maneyrol@tdk.com>,
"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
Subject: Re: [PATCH 3/6] iio: imu: inv_icm42600: Remove redundant error msg on regulator_disable()
Date: Sun, 13 Jul 2025 15:22:00 +0100 [thread overview]
Message-ID: <20250713152200.041e05dd@jic23-huawei> (raw)
In-Reply-To: <20250709-icm42pmreg-v1-3-3d0e793c99b2@geanix.com>
On Wed, 09 Jul 2025 14:35:11 +0200
Sean Nyekjaer <sean@geanix.com> wrote:
> The regulator framework already emits an error message when
> regulator_disable() fails, making the local dev_err() redundant.
> Remove the duplicate message to avoid cluttering the kernel log
> with the same error twice.
>
> Signed-off-by: Sean Nyekjaer <sean@geanix.com>
> ---
> drivers/iio/imu/inv_icm42600/inv_icm42600_core.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/drivers/iio/imu/inv_icm42600/inv_icm42600_core.c b/drivers/iio/imu/inv_icm42600/inv_icm42600_core.c
> index 35f7c66d77790829a739d2c54ba77e53903a9297..55a29b1e2b11355598b0ede7af22857aed3ae134 100644
> --- a/drivers/iio/imu/inv_icm42600/inv_icm42600_core.c
> +++ b/drivers/iio/imu/inv_icm42600/inv_icm42600_core.c
> @@ -700,12 +700,8 @@ static int inv_icm42600_enable_regulator_vddio(struct inv_icm42600_state *st)
> static void inv_icm42600_disable_vddio_reg(void *_data)
> {
> struct inv_icm42600_state *st = _data;
> - const struct device *dev = regmap_get_device(st->map);
> - int ret;
>
> - ret = regulator_disable(st->vddio_supply);
> - if (ret)
> - dev_err(dev, "failed to disable vddio error %d\n", ret);
Dropping this message (which is sensible) reinforces my lack of warm
fuzzy feelings about patch 1. I'd definitely leave those other calls
alone and keep this as just a tight wrapper around st. Note though that
can just pass the regulator as the parameter to the devm_add_action_or_reset()
and simplify this a bit more now you don't need to get to the dev.
> + regulator_disable(st->vddio_supply);
> }
>
> static void inv_icm42600_disable_pm(void *_data)
>
next prev parent reply other threads:[~2025-07-13 14:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 12:35 [PATCH 0/6] iio: imu: inv_icm42600: pm_runtime fixes + various changes Sean Nyekjaer
2025-07-09 12:35 ` [PATCH 1/6] iio: imu: inv_icm42600: Use inv_icm42600_disable_vddio_reg() Sean Nyekjaer
2025-07-13 14:17 ` Jonathan Cameron
2025-07-09 12:35 ` [PATCH 2/6] iio: imu: inv_icm42600: Use devm_regulator_get_enable() for vdd regulator Sean Nyekjaer
2025-07-13 14:19 ` Jonathan Cameron
2025-07-09 12:35 ` [PATCH 3/6] iio: imu: inv_icm42600: Remove redundant error msg on regulator_disable() Sean Nyekjaer
2025-07-10 9:03 ` Andy Shevchenko
2025-07-10 10:47 ` Sean Nyekjaer
2025-07-10 13:07 ` Andy Shevchenko
2025-07-13 14:22 ` Jonathan Cameron [this message]
2025-07-09 12:35 ` [PATCH 4/6] iio: imu: inv_icm42600: Simplify pm_runtime setup Sean Nyekjaer
2025-07-10 9:08 ` Andy Shevchenko
2025-07-10 10:45 ` Sean Nyekjaer
2025-07-10 12:23 ` Andy Shevchenko
2025-07-13 14:28 ` Jonathan Cameron
2025-07-14 7:24 ` Sean Nyekjaer
2025-07-14 7:42 ` Sean Nyekjaer
2025-07-16 8:00 ` Jonathan Cameron
2025-07-18 6:40 ` Sean Nyekjaer
2025-07-19 11:47 ` Jonathan Cameron
2025-07-19 13:32 ` Jonathan Cameron
2025-08-08 13:42 ` Sean Nyekjaer
2025-07-09 12:35 ` [PATCH 5/6] iio: imu: inv_icm42600: Drop redundant pm_runtime reinitialization in resume Sean Nyekjaer
2025-07-09 12:35 ` [PATCH 6/6] iio: imu: inv_icm42600: Avoid configuring if already pm_runtime suspended Sean Nyekjaer
2025-07-10 9:11 ` Andy Shevchenko
2025-07-13 14:32 ` Jonathan Cameron
2025-07-14 10:15 ` Sean Nyekjaer
2025-07-16 8:06 ` Jonathan Cameron
2025-07-10 9:12 ` [PATCH 0/6] iio: imu: inv_icm42600: pm_runtime fixes + various changes Andy Shevchenko
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=20250713152200.041e05dd@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=sean@geanix.com \
/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