From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Cc: Paul Cercueil <paul@crapouillou.net>,
Gwendal Grignou <gwendal@chromium.org>,
Andreas Klinger <ak@it-klinger.de>,
LI Qingwu <Qing-wu.Li@leica-geosystems.com.cn>,
Mike Looijmans <mike.looijmans@topic.nl>,
Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: [PATCH 0/6] iio: PM macro rework continued.
Date: Sun, 7 Aug 2022 19:56:12 +0100 [thread overview]
Message-ID: <20220807185618.1038812-1-jic23@kernel.org> (raw)
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
These are straight forward cases so I've grouped them together.
Aim here is to move to the macros that don't need __maybe_unused markings
and generally simplify the handling of different CONFIG_PM* options.
Jonathan Cameron (6):
iio: proximity: sx9310: Switch to DEFINE_SIMPLE_DEV_PM_OPS() and
pm_sleep_ptr()
iio: proximity: sx9324: Switch to DEFINE_SIMPLE_DEV_PM_OPS() and
pm_sleep_ptr()
iio: proximity: sx9360: Switch to DEFINE_SIMPLE_DEV_PM_OPS() and
pm_sleep_ptr()
iio: proximity: srf04: Use pm_ptr() to remove unused struct dev_pm_ops
iio: accel: bmi088: Use EXPORT_NS_GPL_RUNTIME_DEV_PM_OPS() and
pm_ptr()
iio: light: st_uvis25: Use EXPORT_NS_SIMPLE_DEV_PM_OPS()
drivers/iio/accel/bmi088-accel-core.c | 15 ++++++---------
drivers/iio/accel/bmi088-accel-spi.c | 2 +-
drivers/iio/light/st_uvis25_core.c | 9 +++------
drivers/iio/light/st_uvis25_i2c.c | 2 +-
drivers/iio/light/st_uvis25_spi.c | 2 +-
drivers/iio/proximity/srf04.c | 10 +++++-----
drivers/iio/proximity/sx9310.c | 8 ++++----
drivers/iio/proximity/sx9324.c | 8 ++++----
drivers/iio/proximity/sx9360.c | 8 ++++----
9 files changed, 29 insertions(+), 35 deletions(-)
--
2.37.1
next reply other threads:[~2022-08-07 18:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 18:56 Jonathan Cameron [this message]
2022-08-07 18:56 ` [PATCH 1/6] iio: proximity: sx9310: Switch to DEFINE_SIMPLE_DEV_PM_OPS() and pm_sleep_ptr() Jonathan Cameron
2022-09-18 17:33 ` Jonathan Cameron
2022-08-07 18:56 ` [PATCH 2/6] iio: proximity: sx9324: " Jonathan Cameron
2022-09-18 17:36 ` Jonathan Cameron
2022-08-07 18:56 ` [PATCH 3/6] iio: proximity: sx9360: " Jonathan Cameron
2022-09-18 17:36 ` Jonathan Cameron
2022-08-07 18:56 ` [PATCH 4/6] iio: proximity: srf04: Use pm_ptr() to remove unused struct dev_pm_ops Jonathan Cameron
2022-08-08 9:28 ` Andy Shevchenko
2022-08-08 9:34 ` Paul Cercueil
2022-08-08 9:39 ` Andy Shevchenko
2022-08-08 9:49 ` Paul Cercueil
2022-08-08 10:09 ` Andy Shevchenko
2022-08-08 10:17 ` Paul Cercueil
2022-08-08 10:26 ` Andy Shevchenko
2022-09-18 17:38 ` Jonathan Cameron
2022-08-07 18:56 ` [PATCH 5/6] iio: accel: bmi088: Use EXPORT_NS_GPL_RUNTIME_DEV_PM_OPS() and pm_ptr() Jonathan Cameron
2022-09-18 17:41 ` Jonathan Cameron
2022-08-07 18:56 ` [PATCH 6/6] iio: light: st_uvis25: Use EXPORT_NS_SIMPLE_DEV_PM_OPS() Jonathan Cameron
2022-09-18 17:42 ` Jonathan Cameron
2022-08-08 9:29 ` [PATCH 0/6] iio: PM macro rework continued 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=20220807185618.1038812-1-jic23@kernel.org \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=Qing-wu.Li@leica-geosystems.com.cn \
--cc=ak@it-klinger.de \
--cc=gwendal@chromium.org \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=mike.looijmans@topic.nl \
--cc=paul@crapouillou.net \
/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