From: Jonathan Cameron <jic23@kernel.org>
To: Linmao Li <lilinmao@kylinos.cn>
Cc: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Chris Morgan" <macromorgan@hotmail.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,
"Kanak Shilledar" <kanak.shilledar@axis.com>
Subject: Re: [PATCH togreg v4 0/2] iio: imu: inv_icm42607: fix PM error handling
Date: Mon, 14 Sep 2026 04:05:34 +0100 [thread overview]
Message-ID: <20260914040534.772a4aeb@jic23-hlaptop> (raw)
In-Reply-To: <20260901022243.740760aa@jic23-huawei>
On Tue, 1 Sep 2026 02:22:43 +0100
Jonathan Cameron <jic23@kernel.org> wrote:
> On Mon, 24 Aug 2026 11:55:29 +0800
> Linmao Li <lilinmao@kylinos.cn> wrote:
>
> > The recently queued ICM-42607 PM support has two error paths that can leave
> > the PM core's state inconsistent with the device.
> >
> > Patch 1 propagates sensor shutdown failures from runtime suspend. Patch 2
> > ensures that system resume restores runtime PM management on both of its
> > error paths, so that a failed resume does not leave runtime PM disabled for
> > good.
>
> These look fine to me, but I want input from Chris (and ideally some sanity
> check testing) before picking them up. The dead chicken test that they
> don't active break operation when we don't see errors is probably enough
> given the analysis seems fine to me for what happens on error.
Kanak, given you are looking at this driver perhaps you could take
a look at this series as well?
Thanks,
Jonathan
>
> Thanks,
>
> Jonathan
>
> >
> > Changes since v3:
> > - Patch 1: commit message expanded with the practical effect of the current
> > behaviour, the cost of propagating the error, and a description of the
> > recovery path that does not assume a particular regmap bus
> > implementation. No code change.
> > - Patch 2: unchanged.
> >
> > Neither patch was reproduced on hardware; both were found by code
> > inspection. They were compile-tested with W=1 and checked with smatch.
> >
> > Whether patch 1 is worth making is still a fair question - it trades a
> > possible idle power leak that may be cleared by a later successful access
> > for a runtime PM error state that needs an explicit reset. The commit
> > message spells that out; happy to drop it if you would rather not take
> > that trade.
> >
> > Linmao Li (2):
> > iio: imu: inv_icm42607: propagate runtime suspend errors
> > iio: imu: inv_icm42607: restore runtime PM on system resume errors
> >
> > .../iio/imu/inv_icm42607/inv_icm42607_core.c | 38 ++++++++++++++-----
> > 1 file changed, 29 insertions(+), 9 deletions(-)
> >
> >
> > base-commit: 350d1fb9204b13c5f95e511e98b8bcb47574d425
>
>
next prev parent reply other threads:[~2026-09-14 3:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 3:55 Linmao Li
2026-08-24 3:55 ` [PATCH togreg v4 1/2] iio: imu: inv_icm42607: propagate runtime suspend errors Linmao Li
2026-08-24 3:55 ` [PATCH togreg v4 2/2] iio: imu: inv_icm42607: restore runtime PM on system resume errors Linmao Li
2026-09-01 1:22 ` [PATCH togreg v4 0/2] iio: imu: inv_icm42607: fix PM error handling Jonathan Cameron
2026-09-14 3:05 ` Jonathan Cameron [this message]
2026-09-14 9:23 ` Kanak Shilledar
2026-09-14 14:34 ` Kanak Shilledar
2026-09-15 17:00 ` Chris Morgan
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=20260914040534.772a4aeb@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=kanak.shilledar@axis.com \
--cc=lilinmao@kylinos.cn \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macromorgan@hotmail.com \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®