From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Brian Norris <briannorris@chromium.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
linux-pm@vger.kernel.org, "Ulf Hansson" <ulfh@kernel.org>,
linux-kernel@vger.kernel.org, "Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Jonathan Cameron" <jic23@kernel.org>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Marek Vasut" <marek.vasut+renesas@mailbox.org>,
"Rui Miguel Silva" <rmfrfs@gmail.com>,
linux-iio@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 03/13] iio: Discard pm_runtime_put_autosuspend() return values
Date: Mon, 12 Oct 2026 23:39:50 +0300 [thread overview]
Message-ID: <as1FllpmbCuwLaWi@ashevche-desk.local> (raw)
In-Reply-To: <20261006161337.3.If2263e6ae9eaa4493881b72922dcde031ce9d81d@changeid>
On Tue, Oct 06, 2026 at 04:13:31PM -0700, Brian Norris wrote:
> Multiple IIO drivers inspect or propagate the return value of
> pm_runtime_put_autosuspend(), which is not particularly useful.
>
> Returning an error code from pm_runtime_put_autosuspend() merely means
> that it has not queued up a timer or work item to check whether or not
> the device can be suspended and there are many perfectly valid
> situations in which that can happen, like after writing "on" to the
> device's runtime PM "control" attribute in sysfs for one example.
>
> For this reason, modify these drivers to simply discard the
> pm_runtime_put_autosuspend() return value, and change the return types
> of fxls8962af_power_off() and fxas21002c_pm_put() to void.
>
> This will facilitate a planned change of the
> pm_runtime_put_autosuspend() return type to void in the future, similar
> to commit 3afd8df02433 ("PM: runtime: Change pm_runtime_put() return
> type to void").
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
but see below.
> ---
> This patch is independent of the rest of the series, except for the end
> (changing the return type). I expect it can be applied by individual
> maintainers, and we pick up the end once the dust is settled.
>
> I couldn't decide if I should split this up by individual driver, or
> just 1 for the whole drivers/iio/ subsystem. Many of these drivers have
> borrowed the same patterns, so I chose to just send 1. Let me know if I
> should split it up.
>
> drivers/iio/accel/bmc150-accel-core.c | 14 +++++-----
> drivers/iio/accel/fxls8962af-core.c | 11 +++-----
> drivers/iio/accel/kxcjk-1013.c | 15 ++++++-----
> drivers/iio/accel/mma8452.c | 15 +++++------
> drivers/iio/accel/mma9551_core.c | 15 +++++------
One patch (iio: accel: ...)
> drivers/iio/adc/rcar-gyroadc.c | 4 +--
> drivers/iio/adc/ti-ads1015.c | 8 +++---
Second patch (iio: adc: ...)
> drivers/iio/chemical/atlas-sensor.c | 4 +--
Third patch (iio: chemical: atlas-sensor: ...)
> .../common/hid-sensors/hid-sensor-trigger.c | 14 ++++------
...and so on...
> drivers/iio/gyro/bmg160_core.c | 17 +++++-------
> drivers/iio/gyro/fxas21002c_core.c | 12 +++------
> drivers/iio/imu/kmx61.c | 17 ++++++------
> drivers/iio/light/apds9960.c | 2 +-
> drivers/iio/light/isl29028.c | 15 +++--------
> drivers/iio/light/pa12203001.c | 3 ++-
> drivers/iio/light/rpr0521.c | 15 +++++------
> drivers/iio/light/tsl2583.c | 27 +++----------------
> drivers/iio/light/us5182d.c | 3 ++-
So, I get 7 patches.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-10-12 20:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 23:13 [PATCH 00/13] PM: runtime: Convert pm_runtime_put_autosuspend() and friends to a void function Brian Norris
2026-10-06 23:13 ` [PATCH 01/13] hwrng: cctrng: Discard pm_runtime_put_autosuspend() return value Brian Norris
2026-10-06 23:13 ` [PATCH 02/13] drm: Discard pm_runtime_put_autosuspend() return values Brian Norris
2026-10-06 23:13 ` [PATCH 03/13] iio: " Brian Norris
2026-10-12 20:39 ` Andy Shevchenko [this message]
2026-10-06 23:13 ` [PATCH 04/13] media: venus: " Brian Norris
2026-10-06 23:13 ` [PATCH 05/13] pinctrl: qcom: lpass-lpi: " Brian Norris
2026-10-07 11:44 ` Linus Walleij
2026-10-06 23:13 ` [PATCH 06/13] spi: ti-qspi: Discard pm_runtime_put_autosuspend() return value Brian Norris
2026-10-06 23:13 ` [PATCH 07/13] greybus: " Brian Norris
2026-10-07 14:28 ` Alex Elder
2026-10-07 15:19 ` Brian Norris
2026-10-06 23:13 ` [PATCH 08/13] ALSA: hda: " Brian Norris
2026-10-07 9:45 ` Takashi Iwai
2026-10-06 23:13 ` [PATCH 09/13] ASoC: codecs: lpass: Discard pm_runtime_put_autosuspend() return values Brian Norris
2026-10-06 23:13 ` [PATCH 10/13] ASoC: intel: atom: Discard pm_runtime_put_autosuspend() return value Brian Norris
2026-10-10 9:34 ` Cezary Rojewski
2026-10-06 23:13 ` [PATCH 11/13] ASoC: SOF: Discard pm_runtime_put_autosuspend() return values Brian Norris
2026-10-06 23:13 ` [PATCH 12/13] PM: runtime: Drop pm_runtime_put_autosuspend() return code Brian Norris
2026-10-06 23:13 ` [PATCH 13/13] PM: runtime: Drop pm_request_{idle,autosuspend}() return codes Brian Norris
2026-10-10 8:42 ` (subset) [PATCH 00/13] PM: runtime: Convert pm_runtime_put_autosuspend() and friends to a void function Bartosz Golaszewski
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=as1FllpmbCuwLaWi@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=briannorris@chromium.org \
--cc=dlechner@baylibre.com \
--cc=geert+renesas@glider.be \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=nuno.sa@analog.com \
--cc=rafael@kernel.org \
--cc=rmfrfs@gmail.com \
--cc=ulfh@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
all inboxes | Powered by JetHome®