Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Cc: Paul Cercueil <paul@crapouillou.net>,
	Linus Walleij <linus.walleij@linaro.org>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: [PATCH 0/2] iio: gyro: mpu3050: Cleanup exports and PM
Date: Sun, 20 Feb 2022 17:51:47 +0000	[thread overview]
Message-ID: <20220220175149.503495-1-jic23@kernel.org> (raw)

From: Jonathan Cameron <Jonathan.Cameron@huawei.com>

Paul Cercueil happened to chose this driver as his example for
EXPORT_RUNTIME_DEV_PM_OPS() in his recent patch set to cleanup
how we handle dev_pm_ops.

https://lore.kernel.org/linux-pm/20220105101106.00005ae0@Huawei.com/

Whilst reviewing that I noticed that there were a bunch of exports
in this driver that are only used by other files compiled into the same
module.  Paul found another driver to demo his new infrastructure.

This series is cleaning up that oddity by first dropping the exports
and then using the new pm_ptr() and DEFINE_RUNTIME_PM_DEV_OPS() to allow
the compiler to be responsible for removing the unused code for us rather
than requiring manual CONFIG_PM guards.

Jonathan Cameron (2):
  iio: gyro: mpu3050: Drop unused symbol exports.
  iio: gyro: mpu3050: Use pm_ptr() and DEFINE_RUNTIME_DEV_PM_OPS()

 drivers/iio/gyro/mpu3050-core.c | 14 ++------------
 drivers/iio/gyro/mpu3050-i2c.c  |  2 +-
 2 files changed, 3 insertions(+), 13 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-02-20 17:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20 17:51 Jonathan Cameron [this message]
2022-02-20 17:51 ` [PATCH 1/2] iio: gyro: mpu3050: Drop unused symbol exports Jonathan Cameron
2022-03-15  0:32   ` Linus Walleij
2022-02-20 17:51 ` [PATCH 2/2] iio: gyro: mpu3050: Use pm_ptr() and DEFINE_RUNTIME_DEV_PM_OPS() Jonathan Cameron
2022-03-15  0:33   ` Linus Walleij
2022-06-04 15:56 ` [PATCH 0/2] iio: gyro: mpu3050: Cleanup exports and PM Jonathan Cameron

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=20220220175149.503495-1-jic23@kernel.org \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --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