From: Paul Cercueil <paul@crapouillou.net>
To: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
od@zcrc.me, linux-pm@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Paul Cercueil <paul@crapouillou.net>
Subject: [RFC PATCH 0/3] Introduce pm_ptr() / pm_sleep_ptr()
Date: Tue, 11 Feb 2020 13:03:18 -0300 [thread overview]
Message-ID: <20200211160321.22124-1-paul@crapouillou.net> (raw)
Hi,
I've seen many times things like:
#ifdef CONFIG_PM_SLEEP
static SIMPLE_DEV_PM_OPS(foo_pm_ops, foo_suspend, foo_resume);
#define FOO_PM_OPS (&foo_pm_ops)
#else
#define FOO_PM_OPS NULL
#endif
static struct platform_driver foo_driver = {
.driver.pm = FOO_PM_OPS,
};
And always wondered why there was no of-match-ptr-like macro to make
things cleaner.
So this RFC adds two macros, pm_ptr() and pm_sleep_ptr(), which resolve
to their argument when CONFIG_PM or CONFIG_PM_SLEEP (respectively) are
enabled, or NULL otherwise.
Patch 3/3 is an example of what it would look like when used in a
driver.
Comments welcome.
Cheers,
-Paul
Paul Cercueil (3):
PM: introduce pm_ptr() and pm_sleep_ptr()
PM: Make *_DEV_PM_OPS macros use __maybe_unused
mmc: jz4740: Use pm_sleep_ptr() macro
drivers/mmc/host/jz4740_mmc.c | 12 +++---------
include/linux/pm.h | 16 ++++++++++++++--
2 files changed, 17 insertions(+), 11 deletions(-)
--
2.25.0
next reply other threads:[~2020-02-11 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 16:03 Paul Cercueil [this message]
2020-02-11 16:03 ` [RFC PATCH 1/3] PM: introduce pm_ptr() and pm_sleep_ptr() Paul Cercueil
2020-02-11 16:03 ` [RFC PATCH 2/3] PM: Make *_DEV_PM_OPS macros use __maybe_unused Paul Cercueil
2020-02-11 16:03 ` [RFC PATCH 3/3] mmc: jz4740: Use pm_sleep_ptr() macro Paul Cercueil
2020-02-20 13:38 ` Ulf Hansson
2020-02-20 13:42 ` Ulf Hansson
2020-02-24 15:41 ` Paul Cercueil
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=20200211160321.22124-1-paul@crapouillou.net \
--to=paul@crapouillou.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=od@zcrc.me \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).