diff options
| author | Linmao Li <lilinmao@kylinos.cn> | 2026-08-24 11:55:30 +0800 |
|---|---|---|
| committer | Jonathan Cameron <jonathan.cameron@oss.qualcomm.com> | 2026-09-30 18:59:55 +0100 |
| commit | c1774272c76e92fc3df10a8fedfc033716e55d1b (patch) | |
| tree | 3f13ae7fcf190dd65b5247fe6d9ff34ee7e6834f /tools/lib/python/kdoc/python_version.py | |
| parent | 64c82e7bd9c82b0c9276297df34a3579e8658f55 (diff) | |
| download | linux-next-c1774272c76e92fc3df10a8fedfc033716e55d1b.tar.gz linux-next-c1774272c76e92fc3df10a8fedfc033716e55d1b.zip | |
iio: imu: inv_icm42607: propagate runtime suspend errors
The runtime suspend callback returns success when updating PWR_MGMT0
fails. The PM core then marks the device suspended even though the
shutdown outcome is unknown. If the write did not reach the sensor, the
sensors remain running and draw power while the device is idle.
The condition need not persist. If the bus error clears, a later sensor
access either reads the current PWR_MGMT0 value from hardware or retries
programming the requested enabled mode, allowing normal operation to
resume.
Return the underlying errno to the PM core. -EAGAIN and -EBUSY retain
their transient-error semantics; other errors put runtime PM into an
error state and cause later PM acquires to fail until the status is
explicitly reset. In the normal idle case, a successful system suspend
can perform that reset. This leaves the transient-versus-fatal
classification to the PM core and matches the sibling ICM-42600 driver.
Keep a void wrapper for the managed teardown action, where errors can
only be logged.
Fixes: 3007c1530f96 ("iio: imu: inv_icm42607: Add PM support for icm42607")
Signed-off-by: Linmao Li <lilinmao@kylinos.cn>
Tested-by: Kanak Shilledar <kanak.shilledar@axis.com>
Tested-by: Chris Morgan <macromorgan@hotmail.com>
Signed-off-by: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions
